Clone integration app flows with the template utility

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
• Multi-store to multi-store within the same or different integration tile

Features not cloned and/or supported in the cloning template:

• 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 product 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, Magento 2, 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 Magento 2 - NetSuite Integration App
   4. 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/BigCommerce/Magento 2/Shopify - 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:

• sourceIntegrationID: Enter the source integration app ID from which you desire to clone the setting values and mappings in quotes.
• sourceStoreName: Enter the source store name in quotes. Enter the source store to which mappings and settings should be referenced for cloning in your integration tile. 
• mappingsNotToBeReplaced: Specify the mappings you don’t want to sync to the other integration store in quotes, separating each mapping by a comma. 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.
  Limitation: Be sure to include the below settings that have NetSuite metadata dependency. Settings below the Settings to be ignored field.

  1. NetSuite item to track order taxes as a line item
  2. NetSuite discount item to track line discounts 
  3. Default tax code when no match is found in NetSuite
  4. NetSuite locations to pick inventory from

Scenario 1: Store to stores cloning within the same integration tile: The below setting is applicable only if you're cloning setting and mapping values for stores within the same integration tile:

• storesToBeIgnored: By default, the value of this setting is empty. If you wish to ignore the cloning for any of the stores, mention the store names 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 available stores within the integration tile.
  
  Note:Enter the input details in an array format. Enter each value in quotes separated by a comma.

Scenario 2: Cloning from one integration tile to another integration tile: The below settings are applicable only if you're cloning setting and mapping values for stores from one integration tile to another integration tile:

• destinationIntegrationID: 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.
  
  Notes: 

  • If you don’t provide any destination store name, an error message is displayed.
  • Enter unique integration ID in the sourceIntegrationID and destinationIntegrationID fields if you wish to clone data between different integration tiles.
  • If you enter the same ID in the sourceIntegrationID and destinationIntegrationID fields, the setting values and mappings are cloned from the source store to other available stores (if any) within the same integration tile.

Scenario 3: Multi-store to multi-store within the same or different integration tile: The settings below are applicable only if you're cloning the setting and mapping values for stores between 2 integration tiles. If you are cloning the setting and mapping values for stores in the same integration file, ensure the value in the “sourceIntegrationId” and “destinationIntegrationId” fields should be the same.

• sourceDestinationStoreMap: Mention the source store name on the left hand side in quotes and destination store name on the right hand side in quotes, separated by a comma (as highlighted in the image below)

• sourceStoreName: Enter the source store name in quotes. This action will clone all setting and mapping values for all the stores in the “destinationIntegrationId” field.
  

  Note: If you enter the source store name in this field, any values entered in the “sourceDestinationStoreMap” field will be ignored.

• storesToBeIgnored: Enter the destination stores which should be ignored in quotes separated by a comma.
• You can enter values in both the sourceStoreName and storesToBeIgnored fields to clone the setting and mapping values for the stores in the destinationIntegrationId field. For example, if you have 10 stores in the destinationIntegrationId field and only want to map the settings for 8 stores, enter the source store name in the sourceStoreName field and enter the remaining 2 destination stores that must not be cloned in the storesToBeIgnored field separated by a comma (as highlighted in the image below).

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.