Imports

Import tool is available on Account, Contact, Opportunity (IBO) , Interaction and other form setups.

Administrators can use Import to perform one if the two following mass actions:

  1. import new records
  2. update existing records (UPSERT)

The first column of all import templates contains UUID (a special unique key) of the record in ASPEC.

If this value is left empty, then the Import creates a new record.

If the UUID cell contains a valid value, then the corresponding record will be updated using the column values from the row in the import file.  UUID values can be exported from ASPEC prior to performing UPSERT.  UUID is the first available value in every Export Template.

If any row of the import file fails the validation, the results are displayed in the Import page and none of the rows are imported.  The whole file must pass the validation in order to create new records.

 

Open the Setup section and find the the profile associated with the records type you wish to import.   Click Import button at the top of the profile.  That button opens an Import page.

Fig 1: Button to open the Import tool on Opportunity (IBO) form

The top of the Import page contains the following buttons:

Fig 2: Controls for uploading and validating the import file

  1. Download Import Template: this is the button to downlaod the csv Import Template file.
    Fill out the file and save it to your local drive. Ensure it is saved as a csv file.
    Do not rename or reposition columns in the Import Template.  If you are not sure about the values, scroll down the Import page for more information regarding the format of the fields and the allowed values for dropdown fields, as displayed in Fig. 4 on this page.
  2. Cancel: click this button to cancel the import
  3. Import File: Click Choose file to upload the filled out Import Template.   Make sure that the file is saved as csv and not any other format (.xlsm, .xlsx etc.). Import File Delimiter, Number and Date must match the format configured in the user profile of the person who will be performing the data import.
  4. Ignore required validation: This option applies to required fields when importing NEW records.  More on this option in the next section on this page.   
  5. Validate: clicking this button compares the data in the file with the format required by ASPEC ( spelling, required fields, number and date values etc). Any errors are displayed on the Import page.
  6. Validate and Import: clicking this button compares the data in the file with the format required by ASPEC ( spelling, required fields, number and date values etc).  If all of the data passes the validation, it is imported into ASPEC. The Import page will display the number of imported records when the import is completed.

Clicking Validate or Validate and Import displays a validation feedback.

Validation feedback “Import File Errors” displays a table with the details regarding incorrect or missing data.

Fig 3: Incorrect data in the import file

 

“File Validation Passed” means that all data in the file is correct.

 Note: if you have many errors that don’t seem to make sense, check the file format. Ensure that it is a csv file.

 

New records:

Checking the “Ignore…” option ensures that cells for all required fields are not blank and  filled out correctly.  Required fields must have a value in a correct format.  For non-required fields, the cell can be left blank, but if that cell has a value, it must be a correct value and format.

Unchecking the option allows to import empty cells,as it skips checking if the field is required.  However, if the cell value is not blank, it must have a correct value and format.

Existing records:

Checking and unchecking the option has the same effect. Cells can be left blank, for both mandatory or non-mandatory field.  Validation skips empty cell values and does not override existing fields in existing ASPEC records.

 

To summarize, if the cell is filled out, the imports never accepts a value that inconsistent in value or format.  For new records, the Administrator can choose to allow for empty values for required fields, by checking the “Ignore..” option.

 

Take a look at the three examples below.

In each example let’s assume that a Country dropdown is configured with lookup values “Canada”, “France”, “Germany” and “United States”. It means that users can select one of these four values in the Country dropdown.

Example 1:

If the import file contains an invalid value – e.g. “Spain”. The validation always fails,  for both new and existing records, Country mandatory or not mandatory, and regardless if the “Ignore.. ”  option is checked or unchecked.  “Spain” value does not make sense, unless the value is added to the field configuration prior to the import.

Example 2:

The import file contains value “United States” in the Country column. The validation passes (with the option “Ignore.. ” checked or unchecked), because “United States” is a valid value.

If importing a new record, the result is “United States” in the Country field.

If UPSERTing, the result is “United States” in the Country field, replacing any previous value.

Example 3:

The import file contains an empty value “” in the Country column. The validation depends on the action and mandatory/non-mandatory setup of the field.

If importing a new record, the validation requires that Country if filled out. If passes only if the cell contains a valid value.

If the option to “Ignore..” is checked, the import will create a new records with empty Country field. If If the option to “Ignore..” is not checked, the import will reject this line from the import file.

If UPSERTing, the validating passes,as it does not check against mandatory flag for records that aleady exist in ASPEC.  The result is an unchanged value in the the Country field of the existing record.

 

The bottom of the page lists fields available for the import.

Fig 4: Data description

Required fields are denoted by a red bar, placed to the right of the column header. For example, IBO Status is required.

For Roles field, include the full Role path . Administrator/Europe/France is an example of a role 3 levels deep.

Lookup fields have the allowable values listed in brackets. For example, IBO Status and IBO Products 1 Area are lookup fields. Lookup values must match exactly the values entered in ASPEC setup. For example, Country must match the values configured in the Countries setup, Custom Fields Lookup values must match lists configured in the Lookups section.

Date and numeric fields display the field type in brackets. For example, IBO Closed Date is a date field.

Numeric and date fields must be in a format that matches the User’s Locale Settings and the format of the field.  Note that csv file is a text file, where formatting is not automatically performed as in the MS Excel.  To check the format of values in the import file. open it with  a Notepad/Notepad++ or any other editor that does not format automatically.

Ensure that the date matches the format defined in User Profile and that numbers follow the following rules:

  1. for Integer, the format must match User Profile, but the number of the decimal digits must be 0.  An example of Integer field is Quantity (Products) or any custom field set to be an integer number
  2. for Decimal, the format must match User Profile, but the number of the decimal digits must be 2.  An example of Decimal field is Unit Price (Products) or any custom field set to be a decimal number

UUID ((Universal Unique Identifier), like Source Event UUID in the image aboverequires a special unique value for the linked record.  UUID means a special key, attributed to a record. Each record in ASPEC has its UUID. These values are automatically generated when saving records in the ASPEC interface or when importing them.  This key can be obtained by clicking the Information button of the record, located in the top right corner of the record. Copy and paste that UUID into the import template.  Please also see Linking Object in Import Template by scrolling down this page.

 

Fig 5: Information button

Some records in ASPEC are linked. For example, Contacts are linked to Account, Leads and IBOs are linked to Accounts and Contacts.

Below is the list of UUID used in ASPEC imports.

Note: the records are created or updated if the required fields are filled out in the import file and pass the validation.

Account Imports

UUID Field Affected Object Notes
Account UUID Account that is being imported If empty, a new Account will be created. If filled out, the Account with that UUID is updated.
Parent Account UUID Existing Account, which will be one level higher in Account Structure If filled out and Account UUID is empty, then a new Account will be created under Parent Account if Account required fields are filled out in the import file.

Parent Account UUID does not have any effect if both Account UUID and Parent Account UUID are filled.

 

Contact Imports

UUID Field Affected Object Notes
Contact UUID Contact If empty, then a new Contact is created.

If filled out, then the existing Contact is updated.

Account UUID Account If empty, then a new Account is created.

If filled out, then a new Contact will be created under that Account or the existing Contact moved under that Account.

 

Note: In the imports below, empty Account UUID or Primary Contact UUID indicates the need to create a new Account or Contact. A new Account or Contact is created if the required fields are filled out in the import file and the corresponding UUID is left empty.

Filled out Account UUID and Contact UUID are used only for linking Leads, IBOs, Interactions to Accounts or Contacts. They are not used to override Account or Contact fields with values provided in Lead, IBO or Interactions import files.

Use Account and Contacts imports to update Accounts and Contacts.

Lead Imports

UUID Field Affected Object Notes
Lead UUID If empty, then a new Lead is created.

If filled out, then the existing Lead is updated.

Primary Contact UUID Primary Contact If empt,y then a new Contact is created and it becomes a Primary Contact of the Lead being created.

If filled out, then the new Lead will be created under the existing Contact. The existing Contact will not be updated.

Account UUID Account If empty, then a new Account is created.

If filled out, then a new Lead will be linked to that Account. The existing Account will not be modified.

 

IBO Imports

UUID Field Affected Object Notes
IBO UUID If empty then a new IBO is created.

If filled out then the existing IBO will be updated.

Primary Contact UUID Primary Contact If empty, then a new Contact is created and it becomes a Primary Contact of the IBO being created.

If filled out, then the new Lead will be created under the existing Contact and the Contact will not be updated.

Account UUID Account If empty, then a new Account is created if also Primary Contact UUID is empty.

If filled out, then a new Lead will be linked to that Account. The Account will not be modified.

** if the Marketing module is used, Source Event UUID is also available

 

Interactions Imports

Note: Read more on Interaction Types here.

UUID Field Interaction Type Notes
Interaction UUID If empty, then a new Interaction is created.

If filled out, then the existing Interaction is updated.

Contact UUID Relationship If IBO, Lead and Event Source UUIDs are empty, then Relationship-focused Interaction is created.
IBO UUID Opportunity-focused If filled out, then the result is Opportunity-focused Interaction linked to that Opportunity.
Lead UUID Lead-focused If filled out, then the result is Lead-focused Interaction linked to that Lead.
Source Event UUID Marketing-focused If filled out, then the result is Marketing-focused Interaction linked to that Event.   This options is available only if using Marketing module.

 

 

Import available if using Service module:

Service Request Imports:

UUID Field  Notes
Service Request UUID If empty, then a new Service Request is created.

If filled out, then the existing Service Request is updated.

Account UUID Account linked to the Service Request
Contact UUID Contact linked to the Service Request
Device UUID Device linked to the Service Request

 

Service Order Imports:

UUID Field  Notes
Service Order UUID If empty, then a new Service Order is created.

If filled out, then the existing Service Order is updated.

Service Request UUID “Parent” Service Request