---
schema_version: "1"
id: c083ab0099436710842e546c18adc358e5c03af48223bf4b7b19c9403a47645d
title: Picklist Considerations for Salesforce Connect OData Adapters
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/odata_considerations_picklist.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.odata_considerations_picklist.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 63e09e45aae720a41811c304097749baa5445af07a71032348e44a7a2a383af9
description: Special behaviors and limitations apply to picklist fields on external objects for OData 2.0, 4.0, and 4.01 adapters.
products:
  - Salesforce Platform
  - Security
release: "264"
---
# Picklist Considerations for Salesforce Connect OData Adapters

Special behaviors and limitations apply to picklist fields on external objects for OData 2.0, 4.0, and 4.01 adapters.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition">
      <colgroup>
        <col>
      </colgroup>
      <tbody>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic and Lightning Experience (not for high-data-volume
            external objects)</td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">
            <p>Available in: <strong>Developer</strong> Edition</p>
            <p style="margin-bottom:0;">Available for an extra cost
              in: <strong>Enterprise</strong>, <strong>Performance</strong>, and <strong>Unlimited</strong>
              Editions</p>
          </td>

        </tr>
      </tbody>
    </table>

- 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.

#### See Also

- [Picklist Considerations for Salesforce Connect—Cross-Org Adapter](https://help.salesforce.com/s/articleView?id=platform.xorg_considerations_picklist.htm&release=264.0.0&type=5 "Special behaviors and limitations apply to picklist and multi-select picklist fields on external objects.")