Share
Report
12Hello,
We are having an issue after migrating Dynamics 365 CE On-Prem 8.2 to version 9.1 where Duplicate Detection is not working properly. Everything worked well in 8.2. We have not changed any duplicate detection rules and not modified any security role permissions, yet now when the Duplicate Detection results box opens upon detecting a duplicate, either the results (Potential Duplicate Records) are empty, or the fields that are flagged for duplicates (My Update Record) are empty.
There should be 2 Account records in the bottom box here.
This behavior seems sporadic as sometimes there will be data in both boxes, sometimes there will be data in one or the other, and sometimes both will be empty.
We have tried implementing and removing the Security Role permission for 'Duplicate Detection Rule' as well. It has an effect on the results in these boxes, but doesn't completely enable or completely disable it as we would expect. For instance, in a case where Duplicates Detected shows results in My Updated Record but NOT Potential Duplicate Records, switching the security role permission might reverse what the boxes show - making My Updated Record now empty and now showing records in Potential Duplicate Records.
There doesn't seem to be any one thing we can do to make this function the way it used to and so it is now unreliable for us.
Was there maybe something changed about how Duplicates Detected works from 8.2 to 9.1, or are there new permissions we have to set, or maybe new constraints we need to apply to our existing duplicate detection rules? Are you supposed to rebuild rules when moving to version 9.x? What could possibly be causing this behavior?
Thanks for any help,
Ryan
All responses (
Answers (
