The main purpose of using Data 360 (formerly Data Cloud) related lists in Salesforce is to surface unified, real-time customer data directly on standard or custom records—like Contacts, Accounts, or Cases—without duplicating or storing that data in the core CRM.
On a Contact record, you might add a Data 360 related list showing:
The purpose of this document is to walk through step by step to expose a Data 360 object in CRM to be used by service representative.
Use Case is the Company has purchase orders outside CRM and want it to be visible to their human agents in CRM using Data 360 Related Lists.
In order to follow this guide, you need a Data 360 Sandbox, or other development environment type which is ideally empty of other data to ensure no issues occur with current development practices. A Developer sandbox may therefore be preferred. Data 360 must be activated on the Sandbox to be used.
Note: Data Services Credits will be consumed as part of this exercise.
Download a CSV file that contains contact data, and import it using the Data Import Wizard.
Note: if you need further assistance, see Trailhead here: Import Data to CRM
We will now simulate an upload from a external system, e.g. an on-premise customer database, this will be used to create our unified profile combing Salesforce CRM data to this external data.
We will now import customer transaction data as a CSV, Transaction History .csv, we are simulating this coming from an external system using the CSV upload to speed up the process.
Create the relationship between the transaction History and Individual DMO by clicking the Relationships tab highlighted below.Choose the right cardinality between Transactions and Individual and save the relationship
View your Related List on the contact Page as shown below
Turn On Data 360
Import Data to CRM
Enrich Your Org with 360 Data And Insights
Use Data 360 Related Lists to Enrich Your Contacts and Leads
Enrich Your Applications with Data 360 Data and Insights (Ch. 5)
005101842

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.