Duplicate Detection limitations – Dynamics 365

Some time back, had reblogged about Duplicate detection limitations.

The original post – https://crmfunda.wordpress.com/2018/09/26/d365-limitations-of-duplicate-detection-rules/, talks about the below limitations

Let us check each one of them with the enhanced experience that we now have in the platform

• Duplicate Detection works seamless for Dynamics 365 for Phone app also as shown in the screenshot below.

• Duplicate detection check kicks in when we qualify the lead

Here, qualifying the lead, pops up Duplicate Detection dialog box listing both the matching Account and Contact record.

We can either choose ignore and save to create a new record or click on continue to merge the record with the selected record(s).

• On activating a matching inactive contact record,

Duplicate Detection is not triggered.

Duplicate detection can be setup to run on the following events – 

• While trying to publish 6^th Duplicate Detection rule for Account entity,

we get the below exception

System.Web.HttpUnhandledException: Exception of type ‘System.Web.HttpUnhandledException’ was thrown. —> Microsoft.Crm.CrmException: The selected record type already has the maximum number of published rules. Unpublish or delete existing rules for this record type, and then try again.

Thus maximum 5 duplicate detection rules can be published per entity.

More on Duplicate Detection

Hope it helps..

Author: Nishant Rana

I love working in and sharing everything about Microsoft.NET technology ! View all posts by Nishant Rana