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 6th 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.
2021 Release Wave 1 for Dynamics 365 adds a new Status Reason filter for the Timeline control.
Activity status reason filter will show the status reasons of all the activities in the timeline. For the total 5 activities in the timeline, the filter shows the corresponding status reasons of all the activities divided among Free, Draft, Pending Send, Not Started status.
Another enhancement is in the way the multi-line text field is rendered within the Quick View Form. Now users do not have to click and scroll on the field to see the full content.
Below is the Quick View Form of Contact within the Account entity.
Business Process Flow experience has been updated for the mobile app, making it similar to the web application.
Now – It includes the name and duration for the Business Process Flow within the Mobile App as shown below.
However, as a part of the migration, few steps were still pointing to the old region, which was causing that error. The Microsoft Support / Operation Team quickly corrected it and we were able to configure the Export to Data Lake service without any further issues.
We didn’t face this issue in our Production environment, which was also moved to UAE North.