Skip to content

Commit f4cd6ce

Browse files
committed
Update troubleshooting guide for unified routing: correct date, enhance clarity, and refine resolutions
1 parent 42ff83b commit f4cd6ce

File tree

1 file changed

+9
-8
lines changed

1 file changed

+9
-8
lines changed

support/dynamics-365/customer-service/unified-routing/troubleshoot-enabling-unified-routing.md

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: hbarik
66
ms.reviewer: nenellim
77
ms.topic: troubleshooting
88
ms.collection:
9-
ms.date: 09/17/2025
9+
ms.date: 09/22/2025
1010
ms.custom: bap-template
1111
---
1212

@@ -28,24 +28,25 @@ If you're already using basic routing, issues might occur when you activate or d
2828

2929
## Resolution 1
3030

31-
- Check whether the routing ruleset belongs to a user who no longer has access.
32-
3331
- 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. 
3432

3533
Learn more in [Automatically route cases using basic routing rulesets](/dynamics365/customer-service/administer/create-rules-automatically-route-cases).
3634

3735
## Cause 2
3836

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

4142
## Resolution 2
4243

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

45-
- Delete the record of type msdyn_decisioncontract with the following attributes from your Dataverse instance to complete the provisioning of unified routing successfully.
46+
- **msdyn_name**: Case decision ruleset
47+
- **msdyn_uniquename**: new_incidentmasterentityroutingconfiguration
4648

47-
- **msdyn_name**: Case decision ruleset
48-
- **msdyn_uniquename**: new_incidentmasterentityroutingconfiguration
49+
1. Try to provision again.
4950

5051
Learn more in [Delete record](/power-apps/developer/model-driven-apps/clientapi/reference/xrm-webapi/deleterecord).
5152

0 commit comments

Comments
 (0)