Set Up a CRM Salesforce Org Connection

A data source and data action target are automatically created for the org where you set up Data 360. To connect other Salesforce orgs, you must manually set up a connection.

Required Editions

User Permissions Needed
To access Data Cloud Setup	System admin profile OR Data Cloud Architect

Important Prevent users from logging in to your org via your instanced URL. On the My Domain page in Setup, select Don’t redirect for Instanced URL in the redirections section.

• To ensure a successful CRM connection, configure domain settings in both the source and target org.
• The Salesforce orgs that you connect must have API access and allow access for the Salesforce IP range. See Salesforce IP Addresses and Domains to Allow.
• See Configure User Permissions for an External Salesforce Org Connection in Data 360 and Enable Object and Field Permissions to Access Salesforce CRM in Data 360 .

1. From Data Cloud Setup, select Salesforce CRM under Salesforce Integrations.
2. Click New.
3. Click Connect to a Salesforce org or Connect to a Sandbox org.
4. Click Next.
5. Create an alias for your org by using up to 15 alphanumeric characters. Don't leave this space blank. Select a name carefully, because after the connection is established, the alias can't be changed. The alias is used for data stream and data lake object names. For example, if you use the alias "SourceOrg" and create an Account data stream, you get a corresponding data stream and data lake object named Account_SourceOrg. If you use data kits, note that the alias must match across all orgs.
6. Click Proceed.
7. Log in to the org using your Salesforce credentials.
   The login for a Salesforce production or developer org is https://salesforce.com. The login for a sandbox org is https://test.salesforce.com.
8. In the Allow Access menu, select Allow.
9. Confirm the connection by entering the Data 360 org identifier.
   You can find this ID on the modal under Data 360 Org Details. This specifies which Data 360 org will retrieve data from your source org.
10. Check the checkbox to agree to create the connection and click Connect.
    Your org is now available from the Salesforce CRM Connectors page.

    

    Note After a home org connection is activated, the org can’t be disconnected due to associated system data streams.

• Create a Salesforce CRM Data Stream
  Create a data stream to begin the flow of data from a Salesforce CRM data source to Data 360 for processing and unification.
• Create a Salesforce CRM Starter Bundle
  Create a data stream using a starter bundle to begin the flow of data from a Salesforce CRM source into Data 360.
• Create a CRM Data Stream from Financial Services Cloud (FSC) Objects
  Add the permissions and license requirements in your Salesforce CRM org to ingest FSC objects.
• Install Standard Data Bundles Powered by Data Kits
  After you create your Data 360 instance and set up your Salesforce CRM connection, you can install standard data bundles that are powered by data kits to deploy data within Data 360.
• Set Object Sharing Access for Salesforce CRM
  Sharing access for certain objects, such as QuickTextUsage and MacroUsage, are set to Private by default. To ingest these objects into Data 360, change the organization-wide access to Public.
• Disconnect a Salesforce CRM Connection
  When you no longer need a connection, you can delete it. After you remove a standard Salesforce CRM connection, Data 360 stops ingesting data from the connected org and deletes all the data it ingested from that org, except trust files. Data ingested from the org is removed from unified profiles the next time that identity resolution runs.
• Verify and Reauthenticate a Salesforce CRM Connection
  Verify your Salesforce CRM connection trust and re-authenticate if disruption was caused by a sandbox refresh. If your Salesforce org has a CRM connection to a sandbox org, and that sandbox has recently refreshed, the refresh process generates a new Org ID for the sandbox org that conflicts with the Org ID associated with the existing connection. Because Data 360 can’t establish trust with the refreshed sandbox, the connection to Data 360 is disrupted and requires reauthentication. When the connection is disrupted, data streams associated with it can encounter errors, including deployment failures for new streams and errors within the stream’s refresh history.

See Also

• Salesforce Help: Use an Alias for a Salesforce CRM Connection
• Salesforce Help: Create a Salesforce CRM Data Stream
• Salesforce Help: Configure User Permissions for an External Salesforce Org Connection in Data 360
• Salesforce Help: Enable Object and Field Permissions to Access Salesforce CRM in Data 360
• Salesforce Help: Data 360 Limits and Guidelines