What do you need help with?

Demystifying Picklist Deployments

Follow

Deploying changes to a Standard Picklist field

In order to deploy additions to the option values for standard picklist fields, you will need to deploy both the Custom Field and the StandardValueSet associated with that field. In order to pickup these components, you will need to run a zero day snapshot since they are standard components ideally using the component type filter and component name. 

 Deleted picklist option values will be deployed as InActive values.

Values that have been Deactivated, will get deployed as InActive values. 

This is the list of Standard Picklist fields supported by the Metadata API and only these can be deployed via Flosum. 

The names of standard value sets and picklist fields are case-sensitive.

 

Deploying changes to a Custom Picklist field

When creating a custom picklist field, we have the option of defining the option values from a Global Value Set or within the field itself. 

If you choose the Global Value Set, then you need to deploy the Global Value Set along with the custom field in order for the changes to complete. It has been observed that the last changed on date of a Global Value Set may not change when we add a value to it so you might need to do a 0 day snapshot to retrieve it. 

Deleted picklist option values will be deployed as InActive values whether in field or in Global Value Set.

Values that have been Deactivated, will get deployed as InActive values, whether in field or in Global Value Set.

 

Deploying changes to a Picklist field in a record type

If changes have been made to picklist fields for a record type, then it is necessary to deploy the record type in order for those changes to get deployed on target org. Removed picklist values, Defaults should get deployed. 

 

Dependent Picklist field deployments

Dependency relationships can be deployed by selecting the Dependent picklist. If the dependency is removed in source org, then deploying the Dependent picklist custom field should also remove the dependency. If any dependencies are added or removed from controlling field values, deploying the dependent field should bring all of them across. 

Print Friendly and PDF
Was this article helpful?
0 out of 0 found this helpful

Comments