When your BigCommerce - NetSuite integration app has several BigCommerce stores, you can copy the setting values and mappings of one store, the base store, to the other stores in the same integration app. You do this with the Clone BigCommerce - NetSuite Integration App template, available in the US and EU marketplaces. You choose the base store, and you can exclude specific stores, settings, or mappings from cloning. This article is for integrator.io administrators who manage more than one store.
Prerequisites:
- Install the base store and every destination store in the integration app. For steps, see Add another BigCommerce store.
- Generate an API token at the account level with full access. Go to Resources
, and then select API tokens.
What isn't cloned
The template copies integration app setting values and mappings only. It doesn't copy:
- Saved searches.
- Customizations in your NetSuite account.
- Data from one integration app tile to another, including from sandbox to production or the reverse.
- Installed add-ons.
Install the template
- Go to Marketplace
.
- Select BigCommerce, and then select Install on the Clone BigCommerce - NetSuite template. You can preview the components the template contains.
- In the Install template window, select Install now.
- Read the disclaimer, and then select Proceed.
The setup page opens with the integrator.io connection step.
Set up the integrator.io connection
- For the integrator.io connection, select Click to Configure.
- Select Use Existing Connection and select the connection, or select Setup New Connection and continue with the next steps.
- Enter a name for the connection.
- For Region, select the region of your integrator.io account.
- Enter the account-level API token.
- In the advanced settings, set Concurrency level to
1. Leave the other advanced and custom settings as they are. - Test the connection, and then select Save.
If the connection test fails, check the details you entered. If it still fails, contact Celigo Support.
Choose what to clone
The template's custom settings are in its Settings.
- Integration ID: Replace the default with the ID of the integration app you want to clone within. The integration app doesn't have to be in the same account where you installed the template.
- Base store name: The store whose settings and mappings are copied. Enter the name of one of the stores in your integration app.
- Stores to be ignored: Store names to leave out of cloning, in array format. Empty by default. If you leave it empty, settings and mappings are cloned from the base store to every other store.
-
Settings to be ignored: Labels of settings that aren't cloned. By default, this includes all settings for saved searches, GST and VAT, and the primary lookup criteria for syncing customers. For example, to keep each store's tax code, add the setting label
Default tax code when no match is found in NetSuite. -
Mappings not to be replaced: Mappings that keep their current values in the destination stores. A few required mappings are listed by default. Mappings are grouped by import, and within each import by body-level mappings (
bodyLevel) and by each line-level list. Enter the internal IDs of the fields, which you can find in the import's JSON at/imports/<import ID>.
For example, this Mappings not to be replaced value keeps the subsidiary and currency body-level mappings and the line-level tax code mapping of the NetSuite order import:
"mappingsNotToBeReplaced": { "netsuite-orders-import-adaptor": { "bodyLevel": ["subsidary", "currency"], "item": ["taxcode"] } }Run the cloning flows
- Turn on the Sync base store setting values to other stores and Sync base store mappings to other stores flows.
- Select Run for Sync base store setting values to other stores.
The Sync base store mappings to other stores flow runs automatically after the setting values flow finishes, because the two flows run in sequence.