Resolving validation errors - "Control field value <xxx> not found, valid values are <yyy>"

This Salesforce error that Gearset is surfacing is usually encountered when deploying a picklist or a new value for a picklist.

This is because the metadata that Salesforce uses doesn’t quite line up to what the Salesforce UI would lead you to believe. An example of this is picklist values on standard fields; for instance, the values of the Account Source field on the Account standard object.

The Salesforce UI makes it look as if the field actually stores the value, but the reality is that the values are stored in another metadata type called a Standard picklist value set and the actual field definition for Account Source is only a reference to the Standard picklist value set.

To resolve this issue, update your comparison in Gearset by including Standard picklist value set, Global picklist value set and Custom object metadata types in your metadata filter.

You can then filter the Gearset result and find the changes you're interested in.
​
It may be that you're missing only one of the above metadata types in the filter, in which case make sure they're all retrieved before you re-validate the package in our app.

This validation error is also linked to Picklist value: <xxx> in picklist: <yyy> not found.

The values in the error come from the controlling field, so your comparison needs that field as well as the value sets. Managed packages sit outside the comparison filter by default, so a controlling field inside one is left out even when the value sets are included.

Check both:

Re-validate your package once you have added them.