Clone your integration flows from one integration tile to another integration tile OR within the same tile using a template

You can now clone the Integration App setting values and mappings from one integration tile to another integration tile within the same or different environments (production or sandbox) with one store at a time. You can also clone settings from one store to other stores within the same integration tile using the same template. 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.

Note: As of now, the cloning utility can be installed from the marketplace. This utility entails having an integrator.io license and an unused flow pack. In the future, it is pipelined to be available in the OOTB solution

You can clone your integration app setting values and mappings:

• One store to one or many available stores within the same integration tile.
• One store to another store in a different integration tile of the following environments:
  • Sandbox to sandbox
  • Production to production
  • Sandbox to production
  • Production to sandbox

The integration does NOT allow you to sync the following components:

• Saved searches in NetSuite
• 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.
• In the Amazon - NetSuite Integration App, you can’t clone the list of Categories and its mappings.

Install the template utility

1. Login to your integrator.io account
2. On the left menu, click Marketplace.
3. Choose the appropriate integration, such as Amazon MWS, BigCommerce, or Shopify. 
4. Based on the selected integration, click Install accordingly for one of the following:
   1. Clone Amazon - NetSuite template
   2. Clone BigCommerce - NetSuite template
   3. Clone Shopify - NetSuite template
      
      
5. You can preview the components that are packaged as part of the selected integration.
6. On the “Install template” window, click Install now.
   
   
7. Read the Disclaimer, and accordingly click Proceed.
   
   
   You will be navigated to configure your integrator.io connection.
   

Step 1: Configure integrator.io connection

1. On the “Install app: Clone Amazon/Shopify/BigCommerce - NetSuite integration app page”, next to Step 1, click Configure. 
2. On the “Set up connection” page, you can choose to set up either a new connection or an existing connection.
   1. If you choose to Use Existing Connection, select the connection from the drop-down list.
   2. If you choose to Setup New Connection, proceed with the below next steps.
3. In the Name field, enter your connection name.
4. In the “Application details” section, from the Region drop-down menu, select the appropriate region where the Integration App stores are present. 
   
   
5. Enter the access token generated at the account-level with full access from Resources > API Tokens.
   
6. 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.” 
7. Test the connection and click Save and Close.
   
   Note: If an error is displayed while testing the connection, re-check your details, otherwise contact Celigo Support.

Step 2: Copy resources from template zip file

1. On the “Install app: Clone Amazon/Shopify/BigCommerce - NetSuite integration app page”, next to Step 2, click Install.
   After you successfully install the template zip, you’ll be redirected to the Flows page.
   
   

Understand the custom settings

You can find the custom settings in the “Settings” tab. You will find the following details:

• Source Integration ID: Enter the source Integration App ID from which you desire to clone the setting values and mappings.
• Source store name: Enter the source store name. Enter the source store to which mappings and settings should be referenced for cloning in your integration tile.
• Destination Integration ID: Enter the destination Integration App ID to which tile you wish to clone the data. Enter the destination integration ID in quotes (“integration ID“).
• Destination store name: Enter the destination store name. This setting is invalid if you are cloning the setting and mapping values from one integration tile to another integration tile.
  
  Notes: 

  • If you don’t provide any destination store name, an error message is displayed.
  • Enter a different integration ID in the Source Integration ID and Destination Integration ID fields if you wish to clone data between different integration tiles.
  • If you enter the same ID in the Source Integration ID and Destination Integration ID fields, the setting values and mappings are cloned from one store to another available store (if any) within the same integration tile.

• Stores to be ignored (optional setting): This setting is valid if you are cloning stores within the same integration tile. 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 destination 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 store. By default, few mandatory mappings are specified. All the mappings are segregated below their 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.
  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 to 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

To run the “Sync base store setting values to other stores” flow.

1. Next to the respective flow, click on the on/off toggle button to enable the “Sync base store setting values to other stores” and “Sync base store mappings to other stores” flows.
2. 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 a sequenced flow.