Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
We currently have an entity that holds a relationship between Managers and the Users Both based in the System user Entity. Additionally we have a duplicate detection rule that keys on Ownerid(Manager) , User, and Statuscode. Below is my Configuration of the rule.
The problem is that we have been noticing false firing of the rule above. It appears that the records it is assuming a match to are only a match for 2 of the 3 conditions (User, and Status).
Has anyone else had this issue and or have any suggestions for me here?
That seems unlikely. Please show us the values of the fields on the matched records.
Believe it or not. It happened. I'm not gonna post Names but an equivalent of the situation.
John doe and Jane doe are 2 managers at different locations. George Doe manages accounts at both locations and has 2 managers. He is already set up for Jane doe with the record OwnerID=Jane Does User, User=George Does User, Status Code=1. When creating an instance for John with the record OwnerID= John Does User, User=George Does User, and Status Code=1 It fires the duplicate detection pointing to the earlier instance with Jane doe as the duplicate.
I was able to resolve the issue by disabling and re-enabling the duplicate detection rule. Maybe a race condition got out of sync or something?
Business Applications communities