Field Mapping

to accurately bulk match records between your salesforce instance and altrata, field mappings must be configured between the solutions field mapping must be reviewed before bulk match before initiating bulk match , customers should review field mapping to ensure the proper fields, including foundation ids, are mapped for matching when applicable (for example, in a migration scenario) this helps preserve identity continuity and prevents duplicate matching outcomes confirm field mapping is configured and reviewed confirm foundation ids are mapped and available (especially for migrations) then initiate bulk match by default, the field mapping tab within the altrata settings app will display three object types supported by the solution leads contacts accounts if your instance has person accounts enabled, this will appear as a fourth option it is not required that you enable person accounts for your salesforce instance for the managed package to function if your instance leverages individual object records, this is not currently supported by the managed package fields with a red asterisk are mandatory and must be mapped these will be prepopulated with standard mappings for your convenience; however, verify that those standard fields are leveraged by your instance before proceeding