Comments
In real-world use, duplicate detection cannot account for scenarios like nicknames vs. legal names (e.g., “Blanche” vs. “Bunny”), so duplicates still occur. If Blance Moses is in our system and she interacts online using her nickname of Bunny Moses duplicate detection can't compare "Bunny" to the nickname field already in the system under Blance's record. Someone who doesn't know her will inadvertantly create a new record for her.This makes it especially important that the merge process fully resolves duplicates in a single step rather than leaving inactive records behind.
It's unbelievable that this isn't a feature yet, its been 8 years since this was first posted. We have various products that are all completely the same except for the packaging, and instead of having one item with multiple variants, we have to have different item numbers for the same thing. This does nothing but increase the complexity of our operations. Dynamics team, I'm begging you, please build this already!