Saving the Field Mapping separately from the Scenario in PeopleImport
In PeopleImport, when a scenario is saved it saves all settings from Screen 1 to Screen 5. This makes it easy to use the next time a spreadsheet comes from the same source. The user just loads the spreadsheet and then loads the previously saved scenario. All settings are present and only desired changes need to be made.
For users who have data coming from multiple sources, it is unlikely that column headers will be consistent from one vendor to the next (think: data obtained from Pitney Bowes and how different it could look compared to data obtained from trade-show badge scans). But, just because vendors title data fields/columns differently, that doesn't mean the data is going to a different field in Salesforce.
Data Vendor A names the column holding the phone number, Phone
Data Vendor B names the column holding the phone number, Client Phone #
The PeopleImport User will map both of those fields to the Salesforce Phone field as that is where this information is held - regardless of the column name in the spreadsheet.
If the user loads a spreadsheet from Vendor B and then loads a scenario that was saved after working with data from Vendor A (because the match steps are still in line with how they plan to match Vendor B's data), there is a high potential for this to occur:
An error stating the field couldn't be mapped and, if there are matching conditions that reference the mapping, those will not be generated either.
This happens because the saved scenario is looking for specific field names in the spreadsheet (the mapping saves as part of the scenario). When it can't find them, it alerts the user for manual intervention, i.e. manually mapping the failed fields and creating the failed match conditions.
So, how can a saved scenario be used with a data source with different column headers?
Save the mapping separately from the scenario.
On Screen 1, there is a Save Mapping button that allows the user to save just the field mapping to a separate file. This allows the user to load a mapping and then a previously saved scenario. As long as the mapping is loaded first it will trump the mapping that was saved as part of the scenario. So, the user can load mapping for data from Vendor B and then load a scenario that was created while working with data from Vendor A without issue.
Steps to save the Mapping and use it with a previously saved Scenario:
- Load the file/data source
- Manually map the fields
- Click Save Mapping
- This creates a .PIMXML file (PeopleImport Mapping XML)
- Load the scenario
- Because there is mapping already on Screen 1 this trumps the mapping saved in the Scenario
Steps for using a saved Mapping with a Saved Scenario:
- Load the file/data source
- Load the Mapping
- The Mapping must be loaded before the Scenario
- Load the Scenario
TIP: Create a Mappings sub-folder in the PeopleImport Data folder to easily locate .PIMXML files.
Olivia M.J. Hinkle
Product Adoption Manager