Users can access external objects from the Lightning Experience app. But some requirements and special behaviors apply when the external data is accessed via the OData 2.0, 4.0, or 4.01 adapter for Salesforce Connect.
Required Editions
| Available in: both Salesforce Classic and Lightning Experience |
|
Available in: Developer Edition Available for an extra cost in: Enterprise, Performance, and Unlimited Editions |
-
If external object records don’t appear in your
org, make sure that the OData producer doesn’t change the values specified
in the OData query filters. When your org sends OData queries that specify
field values with the
$filterequals (eq) operator, the OData producer must return those same field values in the resulting data rows. - If external object records don’t appear in relationship fields or related lists, check for case-sensitive values. For example, suppose that you set up an indirect lookup relationship. If the external system uses case-sensitive values in the specified External Column Name, make sure that the parent object field is also case-sensitive. When you define the parent object’s custom field, select External ID, Unique, and Treat "ABC" and "abc" as different values (case sensitive).