Today I have done a lot of reading around duplicate detection and merging in CRM. The source and reasoning for both of these things is clear, but one thing stands out to me as a clear issue. After I have merged two duplicate records, I am still prompted about the existence of a duplicate when updating the parent. I.e. it looks like the default rule for detecting a duplicate continues to consider the Inactive merged record. Isn't the whole point of merging to remove the duplicate prompt? To be extra clear the process is as follows:
- Two active Contacts exist with the same Name and/or Email
- The two Contacts are merged using OOTB functionality (Merge button from view)
- Someone tries to update the Parent Contact (the one that is active)
- A prompt occurs telling the user that a duplicate exists with a link to the Deactivated merged contact
- If they try to merge again, it fails because the Contact is already Deactivated (makes sense)
This is crazy to me. Why does (4) still happen even after merging? Am I missing something?
291,280
