Deploying picklist values via change set causes "Duplicate Label" error
Last updated 2018-05-17 ·Reference W-3689507 ·Reported By 11 users
Customers may experience deployment failures when deploying picklist fields from one spring 17 org to another.
The other related behavior for this bug could be that it allows you to create a new picklist API value with space but once you edit the value to include an underscore you cannot go back and edit the same API value to remove the underscore because of the validation.
1) Create a picklist field with a value "Test value" in the source org, make sure the same value already exists in the target org.
2) Navigate to the source org and notice that you will see the same value for Field label and Field API value
3) Manually edit the API value to include the underscore and save it
4) Now deploy the picklist field from source org to destination org
5) The deployment will fail with "Duplicate Label" error
This happens because currently, we allow both spaces, as well as an underscore as a separator for the picklist API values, when a deployment is done from source org to destination org the picklist field definition considers the same label to be associated with two different API values. It also does not let you edit the API value to remove the underscore because of the validation
R&D has logged a high priority bug to remove the validation that requires an underscore for the picklist field API value.
For a workaround, the customers can delete the picklist value in the source org and create a new one to make sure that the API field value of the picklist contains a space. This will ensure that the field label and picklist values are consistent with definitions in target org when they are deployed and the error can be avoided.
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.