Special behaviors and limitations apply to picklist fields on external objects for OData 2.0, 4.0, and 4.01 adapters.
Required Editions
| Available in: both Salesforce Classic and Lightning Experience (not for high-data-volume external objects) |
|
Available in: Developer Edition Available for an extra cost in: Enterprise, Performance, and Unlimited Editions |
- Global and local single-select picklists are supported.
- You must manually update picklist values to stay in sync between your org and the
external system. If values aren’t in sync, your users could see an error message
when viewing the field.
- Add values to the picklist as you would a picklist on a custom object.
- Remove a value from a picklist by deactivating the value rather than deleting it.
- Replace a value by deactivating it and then adding the new value. Update the external system’s record values to the new value on the external system.
- Convert existing external object text fields to picklists by deleting and recreating. Delete the text field and create a picklist pointing to the text field’s existing External Column Name.
- If you select to delete, you may be prompted to replace the value with another value. No replace occurs for external object record values. You must manually change the values on the external system.
- We recommend having only unrestricted picklists on external objects, even when they’re associated with restricted picklists on the provider org. Restricted picklists on the provider org block unapproved values from the subscriber org, eliminating the need to restrict picklists on external objects.