---
schema_version: "1"
id: 5d0360a7410365f5d548c9d57d13a739edd8304e0ae4d89c04eb8ceed64bede2
title: Socrata™ Considerations for Salesforce Connect—OData 2.0 and 4.0 Adapters
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/odata_considerations_socrata.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.odata_considerations_socrata.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 5d5a1192fa508092086fbbde5367598c73b16d2ab03d9f277414bc5b553cfce2
description: Socrata Open Data Protocol™ is commonly used for health data and for collaboration between governments and their citizens. Salesforce Connect can access data from endpoints that are backed by Socrata Open Data Portal. To accommodate Socrata-specific requirements, set the Special Compatibility field on the external data source to Socrata.
products:
  - Salesforce Platform
  - Security
release: "264"
---
# Socrata™ Considerations for Salesforce Connect—OData 2.0 and 4.0 Adapters

Socrata Open Data Protocol™ is commonly used for health data and for collaboration between governments and their citizens. Salesforce Connect can access data from endpoints that are backed by Socrata Open Data Portal. To accommodate Socrata-specific requirements, set the Special Compatibility field on the external data source to Socrata.

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

Socrata doesn’t support the row identifier (`_id`) column in `$select` or `$orderby` clauses in OData queries. When Socrata is selected in the Special Compatibility field:

- OData queries don’t include the `_id` column in `$select` clauses.
- If an `_id` column is synced from a Socrata endpoint, the resulting custom field on the external object isn’t sortable.
- If you manually define an external object’s custom field with `_id` as the External Column Name, make sure that you select the **Sorting Disabled** attribute for that custom field.

If you modify the Special Compatibility field on an external data source, we recommend that you resync its external objects. Or instead, you can test whether queries or user access to the external objects result in errors, and resync only the problematic external objects.

#### See Also

- [Define an External Data Source for Salesforce Connect—OData 2.0 or 4.0 Adapter](https://help.salesforce.com/s/articleView?id=platform.platform_connect_add_external_data_source.htm&release=264.0.0&type=5 "Connect your Salesforce org to data that’s stored in an external system, such as SAP® NetWeaver Gateway, Microsoft Dynamics® NAV, or IBM WebSphere®.")
- [Considerations for Salesforce Connect OData Adapters](https://help.salesforce.com/s/articleView?id=platform.odata_considerations.htm&release=264.0.0&type=5 "Understand the special behaviors, limits, and recommendations for using the OData 2.0, 4.0, and 4.01 adapters for Salesforce Connect.")