Deployments containing dependent fields fail with Unexpected Error
Last updated Yesterday ·Reference W-6438876 ·Reported By 7 users
When there is a delete operation, or an operation on a soft-deleted field (Field1), in a deployment package with another field (Field2) being updated and dependent on Field1, the deployment will fail with errors observed against Field2 similar to the following:
Error: An unexpected error occurred. Please include this ErrorId if you contact support: 319959797-387280 (-1208708891)
This dependency may take the form of a dependent picklist or a formula field, which is referring to Field1.
The error may also be caused by modification of the search or page layouts in the same package as dependent picklist fields stored on those layouts.
1. Create a custom picklist Field1.
2. Create a second custom picklist, Field2, and set it as dependent on Field1.
3. Within a package deployment, delete Field1 and update Field2 to no longer have a dependency.
This deployment should fail validation, with an error against Field2.
Remove the custom field reporting the error (Field2), and the field on which it is dependent (Field1), from the deployment package and attempt validation again.
The custom fields can then be re-attempted via deployment in a separate deployment package.
Note that while other scenarios in which this error may occur is possible, and is still under investigation, separating the deployment package is the workaround in all cases. If this still fails, contact Salesforce Support.
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.