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 – 

dd

  • 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.

More on Duplicate Detection

Hope it helps..

Advertisements

Set Custom Message and disable background processes inside the Administration mode for Sandbox and Production Environment – Power Platform


Recently while trying to enable Administration mode for one our environments, we realized 2 new options.

  • Background Operations – for disabling any background operations.
  • Custom Message – define the custom message for the users.

For CRM On-Premise, we used to place a custom HTML page + URL
Rewrite during the maintenance window.

Nicely document here – https://debajmecrm.com/dynamics-crm-maintenance-page/

Login to https://admin.powerplatform.microsoft.com/ with System Administrator role, select the Environment, and click on Edit.

Enable the Administration mode, and set the custom message.

Click on Save to make the change, within a minute or so the process will complete.

And the non-system administrator and customizer users will see the below page with our custom message as shown below.

Get more details –

https://docs.microsoft.com/en-us/power-platform/admin/admin-mode

Hope it helps..

Advertisements

Fixed – ClientErrorAborted while creating flow in Power Automate


Recently while creating a flow in Power Automate we got the ClientErrorAborted error.

clientaborted

Users were having all the required licenses / roles.

And only a few users were getting the error, who were accessing the Power Platform from their VDI.

Eventually, after some analysis, we realized that it was because some of the required services were blocked.

We raised the Microsoft Support Ticket who suggested verifying and if required whitelist the below services.

https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/limits-and-config#required-services

Whitelisting them fixed the issue for us.

Hope it helps..

Advertisements

Status Reason filter (Timeline control), Multiline field (Quick View Form) and Improved accessibility for BPF on mobile app – 2021 Release Wave 1


  • 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.

Earlier – 

bpf1

Now – It includes the name and duration for the Business Process Flow within the Mobile App as shown below.

bpf2

Check other blog posts on 2021 Release Wave 1 :

Blog posts on 2021 Release Wave 1 – Dynamics 365

Hope it helps..

Advertisements

DSF Error: CRM Organization cannot be found while configuring Export to Data Lake service in Power Platform


Recently while trying to configure the Export to Data Lake service from the Power Apps maker portal, we got the below error.

DSF Error: CRM Organization <Instance ID> cannot be found.

More on configuring Export to Data Lake service –

https://nishantrana.me/2020/12/10/posts-on-azure-data-lake/

The user through which we were configuring had all the appropriate rights.

https://docs.microsoft.com/en-us/powerapps/maker/data-platform/export-to-data-lake#prerequisites

  • The user had System Administrator Security Role in the CRM Organization/ Dataverse Environment.
  • The user also had the Owner Role on the Storage Account.

Eventually, we raised a Microsoft Support Ticket.

We had recently moved our sandbox CRM Environment from UAE Central to UAE North.

Migrate Dataverse environment to a different location within the same Datacentre region – Power Platform

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.

Hope it helps..

Advertisements

Migrate Dataverse environment to a different location within the same Datacentre region – Power Platform


When we create an environment in the Power Platform admin center, we get the option of specifying the datacenter region, but not the location within it.

Find the Data Center Region / Location of your Dataverse Environment- https://nishantrana.me/2021/04/27/finding-the-datacenter-region-location-of-the-microsoft-dataverse-environment/

E.g. we have specified Region as the United Arab Emirates.

Now within the UAE region, we had our environment created in the UAE Central location. However as per the data residency guide, UAE North should be the main location, and UAE Central is reserved for in-country disaster recovery.

https://azure.microsoft.com/en-in/global-infrastructure/data-residency/

Considering this we had our other Azure Resources / Subscriptions including Storage Accounts, created in UAE North.

However, while configuring the Export to Data Lake service, we got the below message in the Power Apps maker portal.

The storage account must be in the same region as your Dataverse Environment.

Your environment is located in UAE Central

Please attach a storage account in one of the following location(s): UAE Central

Considering our storage accounts were created in UAE North, we either had the option to create a storage account in UAE Central or to move the Dataverse Environment to UAE North from UAE Central.

Based on the recommendation from Microsoft Fast Track Architect and Azure Architects, we opted for the second option of moving the Dataverse Environment to UAE North from UAE Central.

For this, we raised a Microsoft Support Ticket from the admin portal and scheduled the movement for the non-prod environment first.

The movement took around 30 minutes (around 6 GB storage size), however, it was not reflecting in the Power Apps Maker Portal. The Microsoft team had to perform few steps manually in the background which took around 2 more days for the change to reflect in the portal.

Then we scheduled the same for Production (around 15 GB Storage Size), this time it took around the same 30 minutes and after the confirmation from the Microsoft team after 1 hour or so we were able to see the location updated in the Portal (there were no manual configuration steps needed this time) and were able to configure Export to Data Lake service with the storage account located in UAE North.

Posts on Azure Data Lake and Dynamics 365 – https://nishantrana.me/2020/12/10/posts-on-azure-data-lake/

Hope it helps..

Advertisements