Changing a field type to a picklist through change sets doesn't deploy the picklist values
Last updated 2021-05-26 ·Reference W-2242901 ·Reported By 10 users
Changing a field type to a picklist via MD API or change sets doesn't deploy the picklist values
1. In the source org, create a custom picklist field add some values to it e.g. MyField__c.
2. Create a change set in the source org:
a. Add the picklist field from #1
b. Upload the change set to the target org.
3. In the target org, create a custom text (or another non-picklist field) field with the same name as the field in #1.
4. Deploy the change set from #2.
Uploading and Deploying duplicate inbound change sets. First deployment change field type and second deployment reflects picklist values.
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.