Territory Management deployment fails when attempting to deploy changes with other entities
Last updated 2021-10-28 ·Reference W-6392426 ·Reported By 15 users
For example, Territory Management deployment fails when attempting to deploy territory changes if other entities like Account has a list view that is shared to the territory.
Error: "cannot mix EntityObjects with different UddInfos within one transaction"
Note: The issue occurs if the other entity deployed along with the territory references the territory in some way like having a list view that is shared to the territory.
Note: The deployment succeeds when the territory object is deployed separately.
Use your org and make sure you have TM2 enabled and at least one territory created as part of the territory hierarchy (say model name is Model_1 and territory is T_1).
Navigate to Accounts list views and create a list view and share with the territory T_1 created above.
Now perform a metadata retrieve using the package.xml (package.xml shown below).
From set up edit the territory name to say T_1a
Now deploy the package retrieved earlier.
Note the error: UNKNOWN_EXCEPTION: An unexpected error occurred. Please include this ErrorId if you contact support: 1725035668-45666 (845984482)
Deploy the territory changes separately
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.