The clone template utility copies integration app setting values and mappings from one store to another. You can clone from one store to other stores in the same integration tile, or from a store in one integration tile to a store in another tile, in the same or a different environment (production or non-production). You choose the base store and destination stores, and you can exclude specific stores, settings, or mappings from the clone. Use it after a NetSuite sandbox refresh or whenever you need to replicate a working configuration.
Note: The clone utility is installed from the Marketplace. It requires an integrator.io license and an unused flow pack.
Legacy production and sandbox licenses
Warning: In legacy Production and Sandbox environments, the two environments share the same underlying resources. Any resource you create, edit, or delete in one environment is immediately reflected in the other, including connections, imports, exports, flows, scripts, and API tokens. Use caution when editing resources in either environment.
This behavior doesn't apply to accounts on the multi-environment license, where each environment keeps its own isolated resources. If you can toggle between environments, your account hasn't migrated to the multi-environment license yet. See Migrations from the legacy Production/Sandbox license.
What you can clone
You can clone integration app setting values and mappings:
- From one store to one or more stores in the same integration tile.
- From one store to a store in a different integration tile, in any of these combinations: non-production to non-production, production to production, non-production to production, or production to non-production.
- From multiple stores to multiple stores, in the same or a different integration tile.
The following clone templates are available for the US and EU marketplaces:
| Clone type | Templates |
|---|---|
| One integration tile to another | Clone Amazon - NetSuite integration app, Clone Magento 2 - NetSuite integration app, Clone Shopify - NetSuite integration app |
| One base store to one or more stores in the same tile | Clone Amazon - NetSuite integration app, Clone BigCommerce - NetSuite integration app, Clone Magento 2 - NetSuite integration app, Clone Shopify - NetSuite integration app |
| Multiple stores to multiple stores in the same tile | Clone Shopify - NetSuite integration app, Clone Amazon - NetSuite integration app |
Limitations
- The source and destination tiles must use the same NetSuite account. For example, you can't clone a source tile that uses NetSuite account ABC123 to a tile that uses NetSuite account XYZ234. The template matches records by internal ID, and NetSuite field names aren't unique across accounts.
- You can't clone between a tile that points to a NetSuite sandbox and a tile that points to a NetSuite production account.
- The following aren't cloned or supported: NetSuite saved searches, customizations in your NetSuite account, syncing data from one integration tile to another (including non-production to production and the reverse), and installed add-ons.
- In the Amazon - NetSuite integration app, multi-store cloning isn't available by default. To enable it, contact Celigo Support.
- Cloning from a source integration app on the Standard Shopify edition to a target on the Shopify Markets edition clones all components except the Payout tile. Configure the Payout tile, with its settings and mappings, manually.
Prerequisites
- The base store and destination stores are already installed in the integration app.
- To clone between environments, the integration app is installed in both the production and non-production environments.
- Sign in as an account owner or administrator, and generate an account-level access token with full access from Resources > API Tokens. You enter this token when you set up the connection.
- Magento 2 only: Before you run the flows in Clone Magento 2 - NetSuite Integration App, refresh the Magento 2 version setting (Settings > General section > General) in the source and destination tiles.
Install the clone template utility
- Sign in to integrator.io and go to Marketplace.
- Select your integration: Amazon MWS, BigCommerce, Magento 2, or Shopify.
- Select Install for the matching template: Clone the Amazon - NetSuite template, Clone the BigCommerce - NetSuite template, Clone Magento 2 - NetSuite Integration App, or Clone the Shopify - NetSuite template. A preview shows the components packaged in the template.
- In the Install template window, select Install now. The installer opens.
Step 1: Configure the integrator.io connection
- Next to Step 1, select Configure.
- On the Set up connection page, do one of the following:
- To reuse a connection, select Use Existing Connection and choose the connection.
- To create a connection, select Setup New Connection and continue with the next steps.
- Enter a Name for the connection.
- Under Application details, set Region to the region where your integration app stores are.
- Enter the account-level access token you generated from Resources > API Tokens.
- Leave the other Advanced Settings and Custom Settings at their defaults, but in Advanced Settings, set Concurrency level to 1.
- Test the connection, and then select Save and Close. If the test returns an error, recheck your details. If it still fails, contact Celigo Support.
Step 2: Copy resources from the template zip file
- Next to Step 2, select Install.
When the template zip is installed, the Flows page opens.
Configure the custom settings
The clone utility's custom settings are on the Settings tab. Enter text values in quotes, and list values as an array of quoted values separated by commas.
| Setting | Description |
|---|---|
| sourceIntegrationID | The ID of the source integration app whose setting values and mappings you want to clone, in quotes. |
| destinationIntegrationID | The ID of the integration app you want to clone to, in quotes. To clone within one tile, enter the same ID as sourceIntegrationID. To clone between tiles, enter a different ID. |
| sourceStoreName | The source store whose settings and mappings are cloned to the other stores in the same tile, in quotes. Use this setting only for cloning within the same tile. For cloning between tiles, remove it entirely; a blank but present sourceStoreName can cause cross-tile cloning to fail or repeat. When it has a value, any values in sourceDestinationStoreMap and destinationIntegrationID are ignored. |
| storesToBeIgnored | Stores to skip, as quoted names separated by commas. Empty by default, which clones to every other store in the tile. Use only for cloning within the same tile. |
| sourceDestinationStoreMap | Pairs of source and destination stores for multi-store cloning: the source store name in quotes, a colon, then the destination store name in quotes. |
| Destination store name | The destination store for cloning between tiles. If you don't provide one, an error is displayed. |
| mappingsNotToBeReplaced | Mappings that shouldn't be cloned, in quotes and separated by commas. A few mandatory mappings are listed by default. Mappings are grouped under their import and then as body-level or line-level; each list type has its own group, and root-level (non-list) mappings are body-level. Enter the internal ID of each field, which you can find in /imports/<import ID>: body-level fields for body-level mappings, and fields in any list for line-level mappings. |
| Settings to be ignored | Setting labels that shouldn't be cloned. By default, this includes all settings for saved searches, GST/VAT, and primary lookup criteria for syncing customers. Add any other setting labels you don't want cloned. For example, to keep each store's tax code, add Default tax code when no match is found in NetSuite. |
Warning: Settings that depend on NetSuite metadata must be listed in Settings to be ignored: NetSuite item to track order taxes as a line item, NetSuite discount item to track line discounts, Default tax code when no match is found in NetSuite, and NetSuite locations to pick inventory from.
Which settings to use
| Scenario | Settings to use |
|---|---|
| Store to store in the same tile | sourceIntegrationID, sourceStoreName, and optionally storesToBeIgnored. Settings and mappings are cloned from the source store to every other store in the tile that isn't ignored. |
| One tile to another tile | sourceIntegrationID, destinationIntegrationID (a different ID), and the destination store. Remove sourceStoreName; don't leave it blank. |
| Multiple stores to multiple stores | sourceIntegrationID, destinationIntegrationID, and sourceDestinationStoreMap. In the same tile, enter the same value in both ID settings. Between tiles, remove sourceStoreName and storesToBeIgnored. |
Run the clone flows
- On the Flows page, 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.
Sync base store mappings to other stores runs automatically afterward, because the flows are sequenced.