Skip to content

Commit 5e9e075

Browse files
committed
1 parent 3284ff4 commit 5e9e075

File tree

2 files changed

+54
-2
lines changed

2 files changed

+54
-2
lines changed

support/dynamics-365/customer-service/toc.yml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -170,13 +170,15 @@
170170
href: teams-collaboration/flow-connection-invalid-customer-support-swarming.md
171171
- name: Unified routing
172172
items:
173+
- name: Troubleshoot enabling unified routing
174+
href: unified-routing/troubleshoot-enabling-unified-routing.md
173175
- name: Troubleshoot issues with automatic assignment
174176
href: unified-routing/troubleshoot-assignment-issues.md
175177
- name: Dynamics 365 Contact Center (formerly Omnichannel for Customer Service)
176178
items:
177-
- name: Agent Scripts and Macros
179+
- name: Agent scripts and macros
178180
items:
179-
- name: Can't deploy a custom Agent script solution
181+
- name: Can't deploy a custom agent script solution
180182
href: omnichannel-for-customer-service/custom-agentscript-solution.md
181183
- name: Customer summary and Closed conversation form
182184
items:
Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
---
2+
title: Enabling of unified routing fails
3+
description: Learn how to troubleshoot when enabling of unified routing fails in Dynamics 365 Customer Service.
4+
author: hbarik
5+
ms.author: hbarik
6+
ms.reviewer: nenellim
7+
ms.topic: troubleshooting
8+
ms.collection:
9+
ms.date: 09/17/2025
10+
ms.custom: bap-template
11+
---
12+
13+
# Enabling of unified routing fails
14+
15+
This article provides a resolution for the issue where provisioning of unified routing fails and displays an error message. The failure might be on account of various causes, and we provide a set of guidelines for you to troubleshoot this error.
16+
17+
## Symptoms
18+
19+
When you attempt to turn on the unified routing toggle, an error message appears.
20+
21+
## Cause 1
22+
23+
If you're already using basic routing, issues might occur when you activate or deactivate a routing rule set or modify permissions on them.
24+
25+
## Resolution 1
26+
27+
- Check whether the routing ruleset belongs to a user who no longer has access.
28+
29+
- Check the owner of all the basic routing rulesets. If the owner user doesn't have access, then enable the user or update the owner of the basic routing rule set to an active user. 
30+
31+
More information: [Automatically route cases using basic routing rulesets](/dynamics365/customer-service/administer/create-rules-automatically-route-cases)
32+
33+
## Cause 2
34+
35+
The system creates a master entity routing configuration for the Case table as part of provisioning that might fail in copied orgs due to missing related records. Or, when the customer creates the Case master entity record configuration with the same name before triggering provisioning.
36+
37+
## Resolution 2
38+
39+
- Delete the record and try to provision again.
40+
41+
- Delete the record of type msdyn_decisioncontract with the following attributes from your Dataverse instance to complete the provisioning of unified routing successfully.
42+
43+
- **msdyn_name**: Case decision ruleset
44+
- **msdyn_uniquename**: new_incidentmasterentityroutingconfiguration
45+
46+
Learn more in [Delete record](/power-apps/developer/model-driven-apps/clientapi/reference/xrm-webapi/deleterecord).
47+
48+
### Related information
49+
50+
[Enable unified routing in Dynamics 365 Customer Service](/dynamics365/customer-service/administer/provision-unified-routing)

0 commit comments

Comments
 (0)