Import Step

The information on this page relates to the new upgraded interface of the IConduct platform. To view information about the Classic version of the user interface, follow this link.

 

This section describes how to add and set up the connection for the Import step applicable to the tasks in the interface. For more information about steps, see Defining Steps

 

Import step is used to import data into the IConduct Schema for transfer or further manipulation. To create the Import step, navigate to Interfaces> {Specific Interface}> Tasks> {Specific Task} > Steps >New >New Import Step.

 

To import your data from Totara, follow the steps below:

  1. Select your target connection from the Connection drop-down list. Press Open for your reference, or if modifications or any changes are required in the pre-defined connection.

If you can't find the necessary Connection in the list, go to your Connection by clicking Open and make sure the Is Active checkbox is enabled.

  1. Select the required action from the Action drop-down list:
  • Insert: Import new data into an empty Schema’s table.
  • Update: Add the latest data to the existing schema fields.
  • Delete: Delete data from the Schema’s table.
  • Upsert: Select to either update or insert rows of data depending upon whether a specific set of conditions are met (or not).

On selecting Update, Delete, Upsert from drop-down list, the Schema Column and Source Column appear. These fields associate a specific field in the source system to a specific field in the Schema. The rows from the source system will Update/Delete or Upsert rows in the Schema based on this association. Select required columns to enable automatic updates. Press Refresh to update the list of source columns.

  1. Fill in the Query box complying the following format:
  • 1-st row – the entity name;.
  • 2-nd row - entity ID – an internal Totara id used to do the initial mapping;
  • 3rd row (optional) – field - a comma-separated list of fields to query from the entity object in Totara.

When writing the query, make sure to write the field names in lowercase letters and not to put spaces in between fieldnames and commas. Also, the field should be written in one line.

 

Query examples:

The Account entity has two parameters: accountid and fields. The query is compiled as follows:

Account

accountid=2

field=city,country,domain,phone,sfaccounid,state,street,zip,accountname

The Contact entity has two parameters: contactid and fields. The query is compiled as follows:

Contact

conactid=2

filed=firstname,lastname,bucketaccountname,additionalemailmutmcampaign,utmmedium,utmsource,utmcontent

The Opportunity entity has only one parameter – opportunityid. The query in this example should be as follows:

Opportunity

opportunityid=10

The Mimeo entity has two parameters: classid and contactid. The query should be as follows:

Mimeo

classid=2732

contactid=11240

Once done, press Create and proceed with mappings.