I found a little bug related to deploying Field Dependencies from one environment to another. The scenario is as following:
- In Production Org you have defined a field dependency
- In the Sandbox you are having the same field dependency
- You decide to remove the field dependency in the sandbox
- You use DevOps to move this "deletion" of field dependency to the Production Org
- In the Production Org it looks like the Field Depenency has been removed (you cannot see it)
- When you try to test Salesforce still think the field dependency exists
Solution
- Recreate the field dependency (just the name) in production
- Delete the field dependency manually in production
- Hereafter the field dependency is removed 100% from the production
/Henrik
3 Antworten
It is working as intended as per the shared documentation in the comments. We had same issue in maintaining the dependencies correctly. We started using this tool Salesforce dependent picklist matrix export and import extension
We make the changes in dev org, export the dependency matrix using this tool and import it in higher orgs using the same tool. We also commit the exported csv file in the repository to track changes.
