Note: The name “SmartConnector” will be changing to “Integration App” to more clearly establish that our pre-built Integration Apps are built on our flagship Integration Platform as a Service, integrator.io. Find out more about integrator.io.
Setting up the Salesforce-NetSuite Integration App (SmartConnector) involves several steps. The general practice is to configure all the data flows with their respective settings in a Sandbox environment. After the Integration App (SmartConnector) is fully tested, the Production environment is again configured with the same settings. This process involves duplication of effort and requires additional time to get the system up and running.
The new feature of ‘Settings Import/Export’ saves time and effort by enabling an automated copy and move process of all the pre-configured settings of the Integration App (SmartConnector) from the Sandbox environment to the Production environment, or from one NetSuite Account to another NetSuite Account. The solution is designed using a Script and a simple UI is provided to manage the import of the Settings.
Note: All NetSuite and Salesforce custom fields must be created in Production or moved to Production from Sandbox before executing the Import Handler script.
The script is accessible by logging into NetSuite Production as Administrator and can be found under Customization > Scripts > Scripting and Filter the list by bundle - 48893.
Locate Celigo SFNC Settings Import Handler script, click 'View' followed by 'Open Deployments' and click on the URL of Script Deployments:
The URL displays the Import Handler UI (shown below), using the settings needed to be imported between accounts. Login with the source account credentials (account from where you want the Settings and Field Mappings imported). Once logged in, you get access to a set of accounts, from where you can import the Settings. You have the option to import NetSuite and Salesforce Settings separately or both at the same time.
1. From the Authentication Type drop-down list box, select the desired authentication type. You can select Basic or Token.
- For Basic:
i) In the NetSuite Login field, enter an appropriate email ID.
ii) In the Password field, enter the correct password.
iii) From the Environment drop-down list box, select your account type. You can select either a Sandbox or Production account.
- For Token:
i) In the Consumer Key field, enter the appropriate value.
ii) In the Consumer Secret field, enter the appropriate value.
iii) In the Token Id field, enter the appropriate token ID.
iv) In the Token Secret field, enter the appropriate value.
v) In the Account Id field, enter the appropriate value.
2. Click VERIFY CONNECTION. This displays a list of Accounts that the credentials have access to.
3. From the Choose NetSuite Account picklist, select the source Account where you want to import the Settings from.
4. Choose which settings to bring over: Select the checkbox for NetSuite Settings or Salesforce Settings or both.
5. Click IMPORT SETTINGS to begin the import. This process will take a few minutes.
Important Note: The Price Book Mappings are not imported. They have to be manually mapped after the importing is complete. Also, The import works only for the out of the box flows. The custom flows that are configured in Sandbox will not be imported. However, custom field mappings from all out of the box flows are also migrated via the script.
The Import functionality will NOT create any new records in the destination/target.
Before starting the import, ensure that both accounts are a replica of each other, i.e. if there are any custom fields created for mapping in the source systems (usually the Sandbox Environment) they should exist in the destination system prior to executing this script.
If employees are used for team role mapping in the source account, then those employees should exist in the destination account.
If custom fields used for field mapping exist in the source but are missing in the destination, then the import functionality will simple skip them. The field mappings can be added later, after creating/moving the fields.
- Pricebook mapping has to be done manually.