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

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

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.