All Collections
Troubleshooting
Salesforce validation errors
Salesforce validation errors
Resolving validation errors - "Permission <xxx> depends on permission(s): <yyy>"
Resolving validation errors - "Permission <xxx> depends on permission(s): <yyy>"

Validation error "Permission <xxx> depends on permission(s): xxx" was surfaced during a deployment.

Vincent Maltby avatar
Written by Vincent Maltby
Updated over a week ago

Explanation of the error:

In the context of this Salesforce validation error that Gearset is surfacing, <xxx> is the API name for the user permission. Whereas <yyy> is the names of the permission(s) needed for a successful deployment.

Usually, this is auto-enabled when higher level permissions are being granted.

However, when deploying profiles from version control system (e.g. GitHub etc), then the higher level permission may be missed. This is when Salesforce would surface this error on the deployment.

Resolution:

The resolution for this error is to edit the affected user permissions and grant them the <yyy> permissions.

Or if the user permission already has those permissions, try using the default profiles filter:

Further examples of this Salesforce validation error can be found here:
โ€‹Salesforce Stack Exchange

Disclaimer: This error is returned by Salesforce directly, rather than Gearset. Even so, we offer guidance based on our combined experience with the Metadata API. Where possible, we try to help guide you to fix or avoid this error. In the case that this isn't possible, we may need to direct you to Salesforce support for further clarification.

Did this answer your question?