Chapter Mapping
- In this example, the Vault “Chapter” object is mapped to the “Account” object in ChapterSpot/Salesforce.
- Then, the attributes of the Vault Chapter object are mapped to the attributes of the Account object from ChapterSpot/Salesforce.
- See below for an example of how the Vault Chapter object attributes of designation, chapter_type, chapter_code, and university_name are mapped to the ChapterSpot/Salesforce Account object attributes.
- The items in the ChapterSpot/Salesforce picklists populate based on the API calls.
- Chapter mapping only includes one-to-one object/attribute mapping. It does not have any value mapping.
- Chapter objects and attributes only have mapping and matching. It does not have data synchronization like the Member and Officer objects. See the below sections for more details.
- 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.
- User can hover over the question mark beside the “Filter By” field to access Salesforce’s documentation on how to enter this logic.
- The “Preview” button at the bottom of the screen (see the above screenshot) allows you 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