Salesforce Docs Portal

API Names for External Objects and Custom Fields in Salesforce Connect—Cross-Org Adapter

API Names for External Objects and Custom Fields in Salesforce Connect—Cross-Org Adapter

If external objects and custom fields are created in the subscriber org via syncing, their API names are derived from the corresponding API names in the provider org.

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

Each external object’s API name ends with __x. Custom fields on external objects use the traditional __c suffix in the API name. Specifically for objects and custom fields that are synced with the cross-org adapter for Salesforce Connect:

  • For an API name with no suffix in the provider org, the API name is reused in the subscriber org, but with an applied __x suffix for an object or __c suffix for a field.
  • For an API name with a suffix in the provider org, the API name is reused in the subscriber org. But one of the underscores (_) from the original suffix is removed, and a new __x or __c suffix is applied.
Example
Example

If you sync the provider org’s Account object, the subscriber org creates:

  • An external object with the API name Account__x
  • Custom fields including one with the API name Account__x.Name__c

If you sync the provider org’s CustObj__c object, the subscriber org creates:

  • An external object with the API name CustObj_c__x
  • Custom fields including one with the API name CustObj_c__x.Name__c

If the provider org’s object has a custom field, the subscriber org creates the custom field on the equivalent external object, for example:

  • Account__x.MyCustField_c__c
  • CustObj_c__x.MyOtherCustField_c__c

If you sync the provider org’s Account__x external object, the subscriber org creates:

  • An external object with the API name Account_x__x
  • Custom fields including one with API name Account_x__x.Name_c__c

See Also