You are here:
Troubleshoot Data 360 Governance Mergeback Deployments
When you migrate your data governance metadata, you can sometimes encounter deployment errors. Review the symptoms and solutions for common mergeback issues so that you can successfully complete your deployment across environments.
| Issue | Recommended Fix |
|---|---|
| Deployment fails because a record-level security (RLS) policy with joins references a data model object (DMO) or data lake object (DLO) that doesn't exist in the target environment. | Deploy the referenced object first, or include it in the same or an earlier DevOps data kit deployment. |
| Deployment fails because a custom tag assignment is included in the deployment. | Remove the custom tag assignment from the source org, or redesign the policy to use standard tags only. |
| Deployment succeeds, but a policy doesn't appear in the target environment. | Verify that the policy was associated with an object included in the DevOps data kit. Policies aren't deployed independently. |
| Permission error during deployment. | Verify that the deploying user has the Data Cloud Architect permission set in the target environment. |
Did this article solve your issue?
Let us know so we can improve!
