In this example, the Vault “Member” object is mapped to the “Contact” object in ChapterSpot/Salesforce.
The attributes of the Vault Member object are mapped to the attributes of the Contact object from ChapterSpot/Salesforce.
See below for an example of how the Vault Member object attributes of are mapped to the ChapterSpot/Salesforce Contact object attributes.
The items in the ChapterSpot/Salesforce picklists populate based on the API calls.
Member mapping includes both one-to-oneand value The value mapping occurs with the member status attribute, to include member status reason in some cases
You can also filter data to prevent unnecessary records from the Source or Destination systems from pulling into the integration. That logic is entered in the “Filter By” field.
The user can hover over the question mark beside the “Filter By” field to access Salesforce’s documentation on how to enter this logic.
The arrows in the “Sync Direction” column indicate how data flows between the attributes. (As mentioned in the above Chapter section, data sync does not exist for Chapter objects/attributes.) In this example, the data in the specified attributes will flow from ChapterSpot/Salesforce to the mapped attributes in Vault.
Select the appropriate options in the “Sync Operation” field to specify triggers for the data sync and how the updates will be made in the applications. Users can select to only create new records (“Create”), only update existing records (“Update”), or create and update records (“Create/Update”).
Select the “Preview” button at the bottom of the Mapping screen to see an example of how the data will map to the Destination System before activating it.
This is a great way to test your mapping and mitigate errors.
Use the blue arrows above the data sets to scroll multiple records.