Supported integration apps: Amazon, BigCommerce, and Shopify.
You can now clone the existing integration app setting values and mappings from one store to another store within the same integration tile. Additionally, you can overwrite the setting values and mappings from the base store to the selected stores within the integration tile. This utility provides you the feasibility to set the base store and destination stores as per your business needs. You can also choose to ignore the clone feature for any specific stores, settings, or mappings.
Important: This feature is only supported in the integrator.io new current UI
Note: As of now, the cloning utility can be installed from the marketplace. In the future, it is pipelined to be available via the integrator.io platform.
The integration does not allow you to sync the following components:
- Saved searches
- Any customizations in your NetSuite account
- Sync data from one integration tile to another tile (including sandbox to production and vice versa).
- Any installed add-ons.
Install the template utility
- Be sure that the required stores (base store and destination store) are already installed in the existing integration app.
- Before you set up your connection, ensure to generate an access token at the account level with full access from Resources > API Tokens.
- Be sure to check the Developer mode checkbox in My Account > Profile.
- Login to your integrator.io account
- On the left menu, click Marketplace.
- Choose the appropriate integration, such as Amazon MWS, BigCommerce, or Shopify.
- Click Install accordingly for one of the following:
- Clone Amazon - NetSuite template
- Clone BigCommerce - NetSuite template
- Clone Shopify - NetSuite template
- You can preview the components that are packaged as part of the selected integration.
- On the “Install template” window, click Install now.
- Read the Disclaimer, and accordingly click Proceed.
You will be navigated to configure your integrator.io connection.
Set up your connection
- After you installed the template, you will be navigated to the setup page. On the setup page, next to the integrator.io connection, click Click to Configure.
- You can choose to set up either a new connection or an existing connection.
- If you choose to Use Existing Connection, select the connection from the drop-down list.
- If you choose to Setup New Connection, proceed with the below next steps.
- Enter your connection name.
- Select the appropriate region as per your business from the Region drop-down list.
- Enter the access token generated at the account-level with full access from Resources > API Tokens.
- It is recommended to retain the Advanced Settings and Custom Settings as is.
Important: In the Advanced Settings, ensure to select the value of the Concurrency level setting as “1.”
- Test the connection and click Save.
Note: If an error is displayed while testing the connection, re-check your details, otherwise contact Celigo Support.
Understand the custom settings tab
You can find the custom settings in the “Settings” tab. You will find the following details:
- Integration ID: By default, the integration ID is mentioned here that needs to be replaced. Enter the integration app ID in which you want to perform the cloning.
- Base store name: Enter the base store name. You can change the base store name as per the available stores in your integration tile.
- Stores to be ignored: By default, the value of this setting is empty. If you wish to ignore the cloning for any of the stores, mention the store name in this setting. If you do not mention any store name in this setting, the settings and mappings are cloned from the source store to all the other stores.
Note: Enter the input details in an array format.
- Mappings not to be replaced: Below this, specify the mappings you don’t want to sync to the other integration stores. By default, few mandatory mappings are specified. All the mappings are segregated below its respective import. The mappings are further segregated as “body-level” and “line-level.” Each list type will have its own grouping. For non-list (root level), the mappings are mentioned as body-level. See the image below.
Note: Below the “MappingsToBeReplaced” section, enter the internal ID of the fields from the backend code. You can find the actual field names from /imports/<import ID>. As per the import.json, for body-level mappings, refer the fields at the body-level and for the line-level mappings, refer to the fields in any of the lists.
- Settings to be ignored: Specify the label names that should not be cloned to the other integration stores. By default, all the settings related to saved searches, GST/VAT, and primary lookup criteria (to sync customers) are specified. As per your business needs, you can specify any other setting names that should not be cloned to the other store.
Example: If you don’t want to clone the tax code to the other stores, you can add that appropriate setting label name Default tax code when no match is found in NetSuite in this section.
Run the integration flows
Important: Be sure to first run the “Sync base store setting values to other stores” flow.
- Next to the respective flow, click on the toggle button, to enable the “Sync base store setting values to other stores” and “Sync base store mappings to other stores” flows.
- Click Run.
Note: The “Sync base store mappings to other stores” flow automatically runs after the “Sync base store setting values to other stores” flow, as it is sequenced flow.