You can define the available data sources and set the priority of the fields for the data source in beans.
Based on the Salesforce environment that you use, perform one of the following tasks:
In Salesforce Classic, perform the following tasks:
In the upper-right corner of the page, select your name, and click
Setup
.
Under
App Setup
, click
Develop
Custom Settings
.
In Lightning Experience, perform the following tasks:
Click the quick access menu (
), and then click
Setup
.
The
Setup Home
page appears.
Under
PLATFORM TOOLS
, click
Custom Code
Custom Settings
.
The
Custom Settings
page appears.
Select
Manage
for
Data Source Settings
.
The
Custom Setting Data Sources
page appears.
To create a Data Source, click
New
.
The
Data Sources Edit
page appears.
Configure the following components:
Name
Name of the data source or record type.
If the record type is enabled, use the following name format to define data source for one or more record types:
<Data Source>:<Record Type Name1>,<Record Type Name2>,...<Record Type NameN>
For example, SAP:Sales,Marketing indicates that data source definition is applicable to the Sales and Marketing record types.
Check for Duplicates on Create
Optional. Enables
Customer 360 for Salesforce
to check for duplicates when a new record is created. Default is disabled.
Default User ID
Optional. The user identified by this ID is set as the default owner of new account, lead, and contact beans.
Description
Optional. A description for the data source set.
Dynamic Priority
Optional. The API name of the numeric field where the dynamic priority value is stored.
Enable for Search
Optional. Displays the source as a search option in the Account, Lead, and Contact tabs. Default is enabled.
Object Class
Optional. Object class of the data source. For example, Account, Contact, or Product.
Priority Fields
Priority of the source on the corresponding field in beans in the consolidation process. You can set the priority of the fields ranging from 0 to 100. 100 is the highest priority.
If the priority is 0,
Customer 360 for Salesforce
does not update the corresponding field on the consolidated record and the master bean. If the priority is 100,
Customer 360 for Salesforce
updates the corresponding field on the master bean. If beans have an equal priority, the bean with the most current Last Updated Date is used to update the master bean. If the Last Updated is Null, the most current modification date is used to update the master bean.