---
schema_version: "1"
id: be933e75005170dbf13c81e0f0fb0cc3b98943b57d63114ec99392ad96bc22c7
title: API Names for External Objects and Custom Fields in Salesforce Connect—Cross-Org Adapter
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/xorg_api_names.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.xorg_api_names.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 7d62725203e6ca7005f0efdb4519892042d152bfe6d17fc89b9bbe9e62471e62
description: 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.
products:
  - Salesforce Platform
  - Security
release: "264"
---
# 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

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

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](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_click-264-0-0-production-enus/5f7d9219-b7b1-4552-8891-f1aba9b289fc/images/icon_example.png)

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

- [Cross-Org Adapter for Salesforce Connect](https://help.salesforce.com/s/articleView?id=platform.xorg_adapter_about.htm&release=264.0.0&type=5 "Collaborate more effectively and improve processes by connecting the data across your Salesforce orgs. With the cross-org adapter, Salesforce Connect uses Lightning Platform REST API calls to access records in other Salesforce orgs. Nevertheless, setup is quick and easy with point-and-click tools.")