Robust NetSuite Integrator: How to do a conditional field mapping and a few use cases of it?

If you are interested in syncing some of your Shopify order values including its Additional Details to your standard OR custom NetSuite fields in a conditional way, please follow the below-mentioned steps.

Shopify Order JSON

Before we move ahead to a few use cases, this section is all about making you understand how to review the JSON keys i.e. Shopify fields that are holding the values of a Shopify order. Below is a screenshot of what an actual order looks like.

In the above screenshot, we have taken an example of this "Delivery-Date" Shopify field. To review the JSON key of this "Delivery-Date" Shopify field, first click on the URL of this order, and at the end of it, type ".json", further, hit the enter button.

Post clicking you will be seeing something like the screenshot below. In our example, we are interested in reviewing the JSON Key of this "Delivery-Date" Shopify field, and the JSON Key of this Shopify field is this "Delivery-Date".

Note: In majority of the cases, JSON Key will be similar to what you will be seeing in the "Additional Details" section, but it would be good to review it before doing a mapping inside the integrator.

Few Use Cases

Shopify Order Additional Details Mapping - Condition Always

As an example, we are going to sync the value of this "Delivery-Date" Shopify field from an order's "Additional Details" to this "custbody_shipdate" NetSuite custom field always.

Below is the screenshot of a Transaction Custom Field Mapping inside the Robust NetSuite Integrator.

 

JSON Key Explanation

Below is a screenshot to help you understand the complete structure of a JSON Key.

The condition can always be chosen as per your requirements. Below is a screenshot of all the available conditions.

NetSuite Order Source Mapping - Condition (if Shopify order source equals to POS)

As an example, we want to fill the below mentioned NetSuite custom field, but only if the Shopify order source is POS.

Below is an explanation of the above field mapping:

1. NetSuite Custom Field - This NetSuite custom field will be populating the value of this Free-Form Type internal ID 2 NetSuite field. In our case this internal ID belongs to "POS".
   
2. Value Types - This above NetSuite custom field is a Free-Form text type.
   
3. Default option for Field - Internal ID of this Free-Form text type NetSuite field i.e. POS.
   
4. JSON Key Name - Shopify's order source name field.
5. Condition - Fill this above NetSuite custom field, but only if the Shopify order source is POS.
   
6. Condition's Value - POS.

NetSuite Order Class Mapping - Condition (if Shopify order source not equals to POS)

As an example, we want to fill NetSuite's Class field, but only if the Shopify order source is not equals to POS.

Below is an explanation of the above field mapping:

1. NetSuite Standard Field - This NetSuite standard field will be populating the value of this List/Record type internal ID 27 NetSuite field. In our case this internal ID belongs to "Non POS".
   
2. Value Types - This above NetSuite standard field is a List/Record type.
   
3. Default option for Field - Internal ID of this List/Record type NetSuite field i.e. Non POS.
   
4. JSON Key Name - Shopify's order source name field.
5. Condition - Fill this above NetSuite standard field, but only if the order source is not equals to Shopify POS.
   
6. Condition's Value - POS.

NetSuite Order Location Mapping - Condition (if Shopify order source equals to Web)

As an example, we want to fill NetSuite's Location field, but only if the Shopify order source is equals to Web.

Below is an explanation of the above field mapping:

1. NetSuite Standard Field - This NetSuite standard field will be populating the value of this List/Record type internal ID 4 NetSuite field. In our case this internal ID belongs to "Web".
   
2. Value Types - This above NetSuite standard field is a List/Record type.
   
3. Default option for Field - Internal ID of this List/Record type NetSuite field i.e. Web.
   
4. JSON Key Name - Shopify's order source name field.
5. Condition - Fill this above NetSuite standard field, but only if the order source is equals to Web.
   
6. Condition's Value - Web.

In case, you have any questions OR suggestions, feel free to reach out to us at help@webbeeglobal.com.

• Related Articles

• How to place custom segment mapping using Robust NetSuite Integrator ?

  What is Customer Segment ? The Custom Segments feature lets you create custom classification fields similar to class, department, and location. You can create an unlimited number of custom segments, define possible values for each segment, and add ...

• Robust NetSuite Integrator app: Fields Mapping Page Overview

  In our application, we have our USP as Fields Mapping which allows you to map Shopify fields to NetSuite standard/custom fields If you want to (map OR edit) additional fields between your Shopify store and NetSuite account to sync additional ...

• TikTok & Oracle NetSuite Integration via Robust NetSuite Integrator app: Fields Mapping Page Overview

  In our application, we have our USP as Fields Mapping which allows you to map TikTok fields to NetSuite standard/custom fields If you want to (map OR edit) additional fields between your TikTok store and NetSuite account to sync additional ...

• Robust NetSuite Integrator: Complete Feature List

  Complete Feature List This below table shows the compatibility of our integrator with all Shopify & Oracle NetSuite plans. Oracle NetSuite Editions Shopify Plans Robust NetSuite Integrator Support NetSuite NetSuite One World NetSuite CRM NetSuite ...

• Recommended field mapping for the Robust NetSuite Integrator

  Transaction Custom Field To map a NetSuite Custom Field with a Shopify Marketplace field, please follow the below steps: Click on the Add Custom Field button  Further from the Marketplace field drop-down menu, select your preferred Shopify ...