You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/dynamics-365/customer-service/unified-routing/troubleshoot-enabling-unified-routing.md
+9-8Lines changed: 9 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: hbarik
6
6
ms.reviewer: nenellim
7
7
ms.topic: troubleshooting
8
8
ms.collection:
9
-
ms.date: 09/17/2025
9
+
ms.date: 09/22/2025
10
10
ms.custom: bap-template
11
11
---
12
12
@@ -28,24 +28,25 @@ If you're already using basic routing, issues might occur when you activate or d
28
28
29
29
## Resolution 1
30
30
31
-
- Check whether the routing ruleset belongs to a user who no longer has access.
32
-
33
31
- 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.
34
32
35
33
Learn more in [Automatically route cases using basic routing rulesets](/dynamics365/customer-service/administer/create-rules-automatically-route-cases).
36
34
37
35
## Cause 2
38
36
39
-
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.
37
+
One of the following issues can cause a failure in enabling unified routing.
38
+
39
+
- During a copy from an existing org, the decision contract is added in the target org but the related records are missed. When the system tries to [create a master entity routing configuration for the Case table](/dynamics365/customer-service/administer/set-up-record-routing#configure-unified-routing-for-records) during provisioning, it fails because of the missing related records.
40
+
- When the customer creates the Case master entity record configuration with the same name before triggering the provisioning.
40
41
41
42
## Resolution 2
42
43
43
-
- Delete the record and try to provision again.
44
+
1. Delete the record of type msdyn_decisioncontract with the following attributes from your Dataverse instance.
44
45
45
-
- Delete the record of type msdyn_decisioncontract with the following attributes from your Dataverse instance to complete the provisioning of unified routing successfully.
0 commit comments