PeopleImport Scenarios

Scenarios can be created and then saved for future use for imports that use a standard template and matching criteria for importing data.

Capabilities & Features

• Saved on a central server by Salesforce Organization ID for future use
  • Commonly used for weekly webinar lists, standard purchased lists etc.
• Sandbox Org ID's can be linked to Production such that scenarios created on one or the other can be run on either org
• Saved Scenarios will include mapping, along with all the other settings in subsequent stages

Saving a Scenario

Once Stages 1 through 3 are complete, a scenario can be saved by selecting  at the bottom of the screen.


 
1.    Save Scenario as:  Specify a unique scenario name

2.    Category:  Specify a Category to organize scenarios by (similar to a "folder")

• Scenarios can be grouped by Category or any other column

3.    Click Save

• Will be prompted to "replace" if a scenario with the same name exists

Scenarios are saved on a central server by Salesforce Organization ID, NOT on the local PC.

• All the information from each stage is saved in the scenario, including mapping
• If a saved mapping was loaded before the scenarios was loaded (or fields were manually mapped and then a scenario was loaded), this mapping will take precedence over the mapping saved in the scenario
  • A pop-up warning will be displayed if field mapping is different in the loaded mapping from what was in the saved scenario                                                                                                                                                                                                                                                                       

NOTE: If a mapping error occurs, be sure to double-check the matching fields in Stage 3 in case this field was listed as a field to match on, as it will have been removed from the matching step also.

Loading a Saved Scenario

Select  at the bottom of the screen to load a saved scenario AFTER selecting an incoming data source.

• When loading a scenario the Salesforce Org ID that the user logged in on will be displayed at the top of the screen.
• Scenarios can be grouped/organized by dragging any of the column headers to the upper left hand side of the Scenario Screen.
•  Select Load to load the scenario from the server
• Select Delete to delete the scenario from the server
  • Deleted scenarios cannot be restored

Linking Production and Sandbox Instances

• When loading a scenario can select the Linked Scenarios tab to access scenarios saved on a linked organization (e.g. sandbox)
  • To link 2 Salesforce org's together, a request must be made via Validity technical support by emailing support@validity.com
  • Keep in mind that whenever an existing sandbox is refreshed, the old Salesforce org ID is deleted and a new org is created, so a request to re-link the new sandbox will required
  • Once a scenario has been tested in the Sandbox, it is best to re-save it on the Production org, so it can be accessed even when an old sandbox is deleted (refreshed)

Clearing a Scenario

Select  to clear mappings, all selections in Stages 2 - 4, and return all options to their default settings.

• The selected input file will remain loaded
• If matches had been found in Stage 5, these will be cleared also