How to Use *.CSV Import to Trigger NetSuite to Salesforce Flow

These steps should only be used for a relatively small amount of data. For large files (e.g. > 1000 row), Celigo recommends loading data into both NetSuite and Salesforce and then doing ID mapping to populate the NetSuite ID and Salesforce ID fields. 

Reason: The Integration App takes 30 seconds per record, and Salesforce has API limits. 

Scenario 1

You have existing data in NetSuite, and you want to trigger the NetSuite to Salesforce flows to load that data into Salesforce.

Scenario 2

You are loading new data into NetSuite, and you want to trigger the NetSuite to Salesforce flow to load that new data into Salesforce. 

1) Since you are updating existing data in NetSuite, create a new custom field in the NetSuite record.  A checkbox or text field will do.  You just need one field you can safely set.  

2) Create a NetSuite saved search of the records you want to sync. 

Set the filter criteria to select just the records you want to sync.

Display the NetSuite ID field in the output of the saved search. 

Note: For the NetSuite Item to Salesforce Product sync, you will need to create one *.CSV file for each NetSuite Item Type that Celigo has configured for you.  NetSuite requires a separate *.CSV load for each item type, so you would need to create one for Inventory Part, another for the non-inventory part, etc. 

3) Run the saved search, displaying NetSuite ID. This will create a *.CSV file. 

4) Edit the *.CSV file.  Add a column for the custom field you created, and populate the value on each row.  The 2 columns in your *.CSV file will be

1. NetSuite ID
2. New custom field

Note: Excel may be used to quickly add a field value into a column. Then the file should be re-saved as a .CSV, not .xlsx. 

5) Change the *.CSV setting in NetSuite.

Setup - Import/export-import preferences - Check "Run Server SuiteScript and Trigger Workflows".

This allows the *.CSV import to trigger the Celigo sync. 

6) Import the *.CSV file.  (recommended that you try this with a small sample, not your whole *.CSV file.) 

7) This will trigger the Celigo Integration App to run the NetSuite to Salesforce flow, as long as that flow is set up to be triggered on creating or updating. 

8) When the sync is done, change the *.CSV setting in NetSuite.

Setup - import/export - import preferences - uncheck "Run Server SuiteScript".

This prevents future *.CSV imports from triggering syncs. 

Scenario 2: Loading new data into NetSuite

1) Not Applicable - Since this is a brand new *.CSV import (i.e. if the NetSuite items don’t exist), then creating the new field is not necessary. 

2) Create a *.CSV file of the records you want to load. 

Note: For the NetSuite Item to Salesforce Product sync, you will need to create one *.CSV file for each NetSuite Item Type that Celigo has configured for you.  NetSuite requires a separate *.CSV load for each item type, so you would need to create one for Inventory Part, another for the non-inventory part, etc.  

3) N/A for this scenario. 

4) N/A for this scenario. 

5) Change the *.CSV setting in NetSuite.

Setup - Import/export-import preferences - Check "Run Server SuiteScript and Trigger Workflows".

This allows the *.CSV import to trigger the Celigo sync. 

6) Import the *.CSV file.  (recommended that you try this will a small sample, not your whole *.CSV file.) 

7) This will trigger the Celigo Integration App to run the NetSuite to Salesforce flow, as long as that flow is set up to be triggered on creating or updating; or both.  

8) When the sync is done, change the *.CSV setting in NetSuite.

Setup - import/export - import preferences - uncheck "Run Server SuiteScript".

This prevents future *.CSV imports from triggering syncs.