Salesforce CRM Connection Considerations

Understand how the CRM connector maps and processes data, as well as its overall behavior.

• Data Refresh Process for Extraction
  Data refreshes have two phases: full refresh, which replaces all destination data, and incremental refresh, which updates data between full refresh runs. You can perform both full and incremental refresh on demand. Learn about the different refresh scenarios, and the special behavior of ContentVersion and Knowledge_kav objects.
• Mapping for DateTime, Date, and Boolean Objects
  The Salesforce CRM connector maps the objects DateTime, Date, and Boolean based on the object and field type.
• CRM Connector Streaming
  Batch and stream processing handle data differently. Batch mode checks the data once at scheduled intervals of 10-15 minutes, and then processes and stores it in a Data Lake Object (DLO) that you can access. Streaming mode processes data with minimal latency, and reflects changes as soon as they're made in the org.
• Object Support for CRM Data Streams
  When you create a Salesforce CRM data stream, the CRM connector doesn’t support the ingestion of all objects or object types from the connected CRM orgs. Use only supported objects and object types for your data stream.
• Mapping Org IDs
  The internal organization ID is commonly referred to as the Salesforce.com Organization ID or simply the Org ID. It’s a reference ID to the business unit or other internal organization that owns the data record and is a standard audit field for every standard DMO. However, this reference ID value is not populated by the CRM connector.
• CRM Connector Language Behavior
  Keep these considerations in mind when when using the CRM connector.
• Use an Alias for a Salesforce CRM Connection
  As of July ‘24, an alias is required when setting up a Salesforce CRM connection. Existing connections aren't assigned an alias. The names of the data stream and data lake object are derived from the alias.
• CRM Connections in a Sandbox
  Connect your Salesforce org to a sandbox to ensure the safety and integrity of your production environment. When you set up CRM connections from your Salesforce org to a sandbox org, the connections are copied from the production org to the sandbox org.
• Sales and Service Bundle Data Mappings
  Use the Sales Cloud and Service Cloud datasets to manage leads, track progress, and automate sales processes. Sales Cloud data is extracted from Salesforce standard objects, such as Account, Contact, and Lead. The Service Cloud dataset lets you engage your customers at the right time as they go through the support process. These data mappings relate to the Sales Cloud and Service Cloud bundles available for the Salesforce CRM connector.
• Loyalty Management Bundle Data Mappings
  The Loyalty Management data lets you track and manage reward and recognition programs. Loyalty Management is a Salesforce Industry Cloud application. The data is available from Salesforce Platform objects, including Loyalty Program, Loyalty Tier, and Member Benefits. These data mappings relate to the Loyalty Management bundle available in Data 360. You can add more mappings by the bundle, and customize the data mappings. The Loyalty Management bundle is accessible only when object permissions have been set for your Loyalty Management objects.
• Salesforce Commerce Data Bundle Mappings
  Salesforce Commerce standard bundles include Business-to-Business (B2B) Commerce, Direct-to-Consumer (D2C) Commerce, and Salesforce Order Management bundles. These bundles map the data source objects to the data model objects (DMO) and establish DMO relationships that enhance segmentation results.