You can process Salesforce contact records, person account records, relationship records, and hierarchy records with Customer 360 SaaS in batches.
Using the parameter file
A parameter file is a list of user-defined parameters and their associated values. Use the parameter file to define values that you want to update without having to edit the mapping task. The parameter values are applied when the task runs.
The Customer 360 Extension for Salesforce package contains the following parameter file in the Secure Agent files directory for the Data Integration mappings:
After importing the assets, configure the Customer 360 connection.
1In Administrator, click Connections.
2Click infac360sf_conn_customer360.
3Test the connection, and ensure that the connection is successful.
Configuring the Salesforce connection
After you configure the Customer 360 connection, configure the Salesforce connection.
1On the Connections page, click infac360sf_conn_salesforce.
2Click Edit, and enter the credentials to access Salesforce.
3Test the connection, and ensure that the connection is successful.
Configuring Business 360 FEP connector
You can use the Business 360 FEP connector to write Salesforce data into Business 360. If the input values for Salesforce integer fields are null, the Business 360 FEP connector converts the null values to 0 in Business 360.
1In Administrator, click Connections.
2Click infac360sf_conn_customer360.
3Test the connection.
The connection might fail with the following error:
The test connection for infac360sf_conn_customer360 failed. Unable to fetch connector attributes, Ensure adapter ID is valid[com.infa.adapter.mdmflat].
4If the connection fails, verify and ensure that the connection is successful.
aVerify the license used.
bEnsure that the connector is enabled for the Secure Agent group.
cRestart the Secure Agent.
Synchronizing source and target objects of mappings
Before you run the predefined mappings, ensure that you synchronize the source and target objects of the inbound and outbound mappings. Synchronizing source and target objects helps you avoid import and export failures.
1Synchronize the source objects for all the inbound mappings.
aIn Data Integration, click Explore > Customer360 > Salesforce Extension.
bNavigate to an inbound mapping. For example, infac360sf_m_salesforce_contact_person_inbound_phone.
cOn the Design page, select a source object of the mapping.
dOn the Source tab, select the infac360sf_conn_salesforce connection.
The p_src_system_connection connection is selected by default.
eOn the Fields tab, click the Synchronize icon.
The Synchronize window appears.
fSelect All fields, and click Synchronize.
gOn the Source tab, select the p_src_system_connection connection, and click Save.
hRepeat steps 1a through 1.g for other inbound mappings.
2Synchronize the target objects for all the outbound mappings.
aIn Data Integration, click Explore > Customer360 > Salesforce Extension.
bNavigate to an outbound mapping. For example, infac360sf_m_salesforce_person_contact_outbound.
cOn the Design page, select the target object of the mapping.
dOn the Target tab, select the infac360sf_conn_salesforce connection.
eOn the Target Fields tab, click the Synchronize icon.
fSelect the fields to synchronize.
gOn the Target tab, select the p_src_system_connection connection, and click Save.
hRepeat steps 1a through 1f for other outbound mappings.
Exporting value mappings of crosswalk (optional)
If you have changed the crosswalk values in Reference 360, export the value mappings of the Country and State crosswalks to a CSV file.
1In Reference 360, under Explore, expand Country > Enterprise Country > Salesforce Country to Enterprise Country.
2Click the Export Mappings icon.
3Enter the file name as Country_ISO_Conversion.csv and click Export.
4Click Explore > State > Enterprise State > Salesforce State to Enterprise State.
5Click the Export Mappings icon.
6Enter the file name as State_ISO_Conversion.csv and click Export.
7Save the downloaded files in the following directory:
Associating picklist fields with reference data code lists
To associate the picklist fields with the reference data code lists for the Organization and Person business entities, configure the Salesforce source system.
3To associate the picklist fields with the reference data code lists for a business entity, click the Add an asset icon.
4Select the business entity.
You can select the Organization or Person business entity to associate the picklist fields with the reference data code.
5Click Select.
The Select an Asset page opens.
6Select the corresponding code list for a picklist field.
The following table shows the picklists with the associated code lists for the business entities:
Picklist
Code List
Address:Country
Salesforce Country
Address:State
Salesforce State
7Click Save.
Exporting records created in Customer 360 to Salesforce
To enable exporting of records created in Customer 360 to Salesforce, perform the following steps:
1In Data Integration, click Explore > Customer360 > Salesforce Extension.
2Navigate to an outbound mapping. For example, infac360sf_m_salesforce_person_contact_outbound.
3On the Design page, select the target object of the mapping.
4On the Target tab, select the Upsert (Update or Insert) operation.
5Select the Use ID Lookup option.
6From the ID list, select Id, and click Save.
Configuring change data capture
Customer 360 Extension for Salesforce uses the change data capture option to identify the changed records and process them in the incremental data loads. By default, the change data capture option uses the date and time when the record was last modified and the date and time when the record was last synchronized with Customer 360.
You can change the default condition to identify the data change based on your requirement.
Default change data capture condition
The default condition contains multiple conditions joined by the OR operator.
The following expression shows the default condition:
lastmodifieddate>$$LastExtractedDate OR (customer360_Sync_Date__c<$$v_previous_session_start_time OR customer360_Sync_Date__c=NULL)
The expression uses the following conditions:
•lastmodifieddate>$$LastExtractedDate. Identifies records that are created or updated after the maximum timestamp of the previously processed records.
•customer360_Sync_Date__c<$$v_previous_session_start_time. Identifies the records failed during the previous incremental load.
•customer360_Sync_Date__c=NULL. Includes all records for the initial load. It also identifies records failed during the initial load.
The default condition considers all three scenarios.
Customizing change data capture condition
You can customize the default condition based on your requirements. You can parametrize the condition to override the default condition by passing a different condition to the in-out parameter.
You can customize the condition by using one of the following methods:
•Update the v_source_filter_condition in the parameter file of the mapping task.
•Edit the current value of the v_source_filter_condition in the mapping task.
1On the Explore page, navigate to the mapping task.
2Click Edit.
The mapping task wizard opens.
3Navigate to the In-Out Parameters page.
4From the Action column and in the row that contains the parameter, click Edit.
The Edit In-Out Parameter dialog box opens.
5Set the value.
6Click OK.
By default, the mapping task retains the value set during the previous run.
Customizing the parameters for change data capture
You can customize the parameters in the parameter file of a mapping task based on your requirement.
The input parameters can be configured only by editing the mapping task. The in-out parameters can be configured through parameter files or by editing the mapping task.
The following table lists the in-out parameters that you can configure in the mapping task:
Name
Data Type
Length
Default Value
Description
LastExtractedDate
String
255
1900-01-01T00:00:00Z
Date and timestamp of the last time mapping run. For the first mapping run, the parameter uses the default value. The parameter stores the updated maximum value after every run.
v_previous_session_start_time
String
255
1900-01-01T00:00:00Z
Start time of the previous run of the mapping task.
Uses the timezone of the Secure Agent on which you run the taskflows.
v_source_filter_condition
String
1000
lastmodifieddate>$$LastExtractedDate OR (customer360_Sync_Date__c<$$v_previous_session_start_time OR customer360_Sync_Date__c=NULL)
Condition that identifies the changed records and processes them in the initial and incremental data loads.
Running the jobs
After integrating Salesforce and Customer 360, you can run the ingress and export jobs.