Fixed – Unable to add record type ‘Lead’. It is invalid to create component msdyn_decisioncontract with the same export value as an existing component in Unified Routing (Dynamics 365)

Recently while trying to enable Unified Routing on Lead table/ entity we got the below error.

“Unable to add record type ‘Lead’. It is invalid to create component msdyn_decisioncontract with the same export value as an existing component

The issue was that the we forgot to enable the unified routing on lead before migrating lead related unified routing records in that environment, from the development environment.

So as per the details in the error message, we found the below record and deleted it.

After deletion it allowed us to enabled the Unified routing on Lead as shown below.

Hope it helps..


How to – Provision Unified Routing in Dynamics 365 Customer Service Hub

Unified Routing can be configured in Customer Service Hub or Omnichannel Admin Center.

To configure it for Dynamics 365 Customer Service, navigate to

Service Management >> Service Configuration Settings >> Unified routing

(requires Tenant administrator’s consent – click on Provide Consent link)

Accept the permissions requested and provide the consent.

In case unified routing remains disabled  –

Unified Routing once switched on, cannot be disabled from the application, and we need to contact Microsoft Support to turn it off.

The provisioning starts

After a couple of hours, we can see Unified Routing configured for the Customer Service app.

We can see the following solution – Anchor solution for UnifiedRoutingForCS in Dynamics 365 solutions installed in the environment.

Hope it helps..



Solved – Disabled Turn on unified routing option in Dynamics 365 Customer Service Hub

Recently while trying to provision Unified Routing from Dynamics 365 Customer Service Hub in one of our trial environments (Service Management >> Service Configuration >> Unified Routing – Turn on unified routing.),

even after providing the consent multiple times (by clicking on Provide consent, with Global Admin role)

it kept coming as disabled and kept asking for providing the consent.

Opening in in-private browsing or a different browser didn’t fix it.

Clearing the cache also didn’t help – Empty Cache and Hard Reload

The trick that worked here was creating a workstream record

which also triggered the provision of Unified Routing 

And after our workstream record got created,

we could see the unified routing enabled successfully.

Hope it helps..

%d bloggers like this: