Export Step
This section describes how to add and set up the connection for the Export step applicable to the tasks in the interface. For more information about steps, see Defining Steps
The Export step allows exporting entities from IConduct to NetSuite. To create the Export step, navigate to Interfaces> {Specific Interface}> Tasks> {Specific Task}> Steps >New >New Export Step.
To export your data, follow the steps below:
- Select your NetSuite API connection from the Connection drop-down list. Click Open for your reference, or if modifications or any changes are required in the pre-defined connection.
Warning: If you can't find the necessary Connection in the list, go to the connection page and make sure the Is Active and Is Target checkboxes are enabled.
- Select the target entity from the Entity Name drop-down list.
- Select the required action from the Action drop-down list.
- Insert: Put data into the end-point table.
- Update: Add the latest data to the existing end-point field.
- Delete: Delete data from the end-point field.
- Upsert: Depending on the key- either update or insert data to the end-point field.
Note: On selecting Update, Delete, Upsert from the Action drop-down list, the Schema Column and Source Column appear. These fields associate a specific field in Schema to a specific field in the target system. The rows from Schema will Update/Delete or Upsert rows in the target system based on this association. Select required columns to enable automatic updates.
Warning: Working with the "Upsert" action make sure to select externalID in the Schema Column and Source Column and map these fields at Schema Mappings.
- Once done, press Create and proceed with mappings.
Warning: For a correct data transition to NetSuite, all fields containing IDs in the field name are mandatory for mappings in all entities.
Note: At Customer entity, the customer may be an individual or a legal person. In case the customer is a legal person, the “CompanyName” field should be mapped. By default, the customer is a legal person and the “IsPerson” field has the value ‘false’. If the customer is an individual, the value for the “IsPerson” field should be set to ‘true’ and the “FirstName” and “LastName” fields become mandatory for mappings.