You can clone your Salesforce-NetSuite (IO) integration app setting values and mappings from one integration tile to another integration tile of different environments. If you have the Salesforce - NetSuite IO integration apps in the production and sandbox environments, the integration app provides feasibility to choose the environment.
Important: This feature is only supported on the integrator.io current UI.
The cloning feature is also helpful if you have to verify any features in the sandbox environment. In this scenario, you can directly clone the integration tile from the production environment to the sandbox environment.
You can clone your integration app between the following environments:
- Sandbox to sandbox
- Production to production
- Sandbox to production
- Production to sandbox
The below table explains the components that are cloned and not cloned from the base integration tile to the source integration tile:
|
Cloned |
Not cloned |
|
|
Information: The cloning capability will be available for the saved searches in future releases.
Checklist after you clone
- Check all the settings where you select the Salesforce or NetSuite specific components.
- Click the refresh icon for all the settings wherever applicable, select the appropriate option, and save the settings.
- Check all the required custom fields.
Clone your integration app
- Login to your integrator.io account.
- Select the Salesforce - NetSuite (IO) integration tile you wished to clone.
-
On the top-right, click Clone integration. You are redirected to the cloning page.
-
On the cloning page, in the Tag field, enter the name of the cloning integration app.
Notes
- By default, in the Tag field, the existing integration app name is prefixed with “Clone.” If your existing integration app name is “Salesforce - NetSuite,” in the Tag field while cloning, you will see “Clone - Salesforce - NetSuite.”
- You cannot have the same names for the source and destination tiles.
-
Choose the Environment to which you wish to clone your existing integration app.
Notes- The Environment option is available only if you have the Salesforce - NetSuite IO integrator.io subscription in the production and sandbox environments. Once the integration app is cloned and if you try to enable any flow, the integration app license is validated.
- You can read through the components that are cloned as part of this integration such as integration, flows, imports, exports, and connection details.
- Click Clone integration.
Configure and install your destination integration app
Prerequisite: Before you begin to configure the destination integration app, be sure that you have a valid integration app license. However, you will be able to clone the integration app and when you try to enable any flow, the integration app license is validated.
Note: If you wish to cancel your installation, you can click Uninstall on the top-right.
Step 1: Configure your NetSuite connection
You can authenticate your connection either using the basic, token, or automatic token options. We recommend you to use any of the token-based authentication methods. For token-based authentication, create an access token in NetSuite. After you configure, you won't be able to change the NetSuite environment and account.
Step 2: Configure your Salesforce connection
Prerequisite: The new Salesforce account users are recommended to install the packages and enable/disable the flows to back up the real-time SObjects.
Lets you create a connection with Salesforce. You can authenticate your connection either using the Refresh Token or JWT Bearer Token option. Once you allow access with your Salesforce account credentials, you won't be able to change the Salesforce configuration. You can change the account or account type after you completely install the integration app.
Note for step 3 to step 6: You have to manually verify the Salesforce integrator.io package, Salesforce integration app package, NetSuite integrator.io bundle, and NetSuite integration app SuiteApp.
Step 3: Install the integrator.io package in Salesforce
It is recommended to install using the Install for All Users option. After you install, an email is sent and you can find the installed package on the Salesforce > Installed Packages page. Verify your package after installation.
Step 4: Install the NetSuite package in Salesforce
It is recommended to install using the Install for All Users option. After you install, an email is sent and you can find the installed package on the Salesforce > Installed Packages page. Verify your package after installation.
Step 5: Install the integrator.io bundle in NetSuite
Lets you install the integrator.io bundle (20038) in NetSuite. It is a common bundle across all integration apps. Verify the bundle. If you already have a bundle installed, it is either updated or auto-verified. It is recommended to update and verify the bundle from NetSuite > Installed Bundles page.
Step 6: Install the Salesforce SuiteApp in NetSuite
Lets you install the Salesforce SuiteApp in NetSuite. You can install and verify the SuiteApp in NetSuite.
Step 7: Copy resources now from template zip
In this step, clone all the information related to the source tile such as mappings, advanced setting values, imports, exports, and connection details from the source tile to the destination tile.
Information: It is expected that the “Copy resources now from template zip” step might take a long time as it is migrating the information from the source tile to the destination tile.
Understand the destination tile
Important: After you clone your integration tile, it is recommended that you verify all the mappings, settings, saved searches before you sync data between Salesforce and NetSuite.
After you clone, when you try to enable the flow, the integration app license is validated. If you do not have a valid license, then the integration app displays an error message when you try to enable any flow.
After cloning, the saved search value is set to the default value. It is recommended to verify all the saved searches and update the value accordingly. This is also applicable for the saved search filters if any.
Go to
- Configure Product > NetSuite to Salesforce > Salesforce Standard Price Book - for this setting you have to check and uncheck the Active checkbox in your Salesforce account to reflect the appropriate changes in your integration app. Internal ID that is populated in the Salesforce account URL might vary in the source and destination tiles.
- Map NetSuite Price Level to Salesforce Price Book - If you refresh the Salesforce Price Book, then in this setting you might have to reconfigure your values.
- For the NetSuite components, the internal ID might change. It is recommended that you refresh and reset the values again.
- If the user is using any default fields that are provided by our package, then you might not have to re-configure those settings. All the values as per our package will be cloned. If you are using any other field, then you have to re-configure that setting again.
Contract-renewals add-on
If your source tile has the contract renewal add-on, it is cloned to the destination tile. After cloning, when you try to enable the add-on flow, the add-on license is validated. If you do not have a valid license, an error message is displayed.
Note: If your source tile has the “contract renewal” add-on and in your destination tile, the NetSuite account you configured has the “contract renewal” feature disabled, cloning fails and the entire integration app is not cloned.
Comments
1 comment
How does the cloned integration differ in terms of customizing? Am I able to access the features that are locked down on the original app, for instance, Java hooks and transformations?
Please sign in to leave a comment.