NetSuite Data Mapping

Data Mapping and Transformation is one of the powerful features of Connect iPaaS. When you create a workflow, certain data points of your Trigger application are available in the Action application for data mapping and in NetSuite's case, sub-attributes too. This makes up a comprehensive list of attributes to choose from.

These Data Mapping can be mapped to the specific attributes of the Action application. This powerful capability not only allows field mapping for business users but also the complex transformation using excel style functions with hundreds of formulas and operations.

Example Scenario 1 with NetSuite Trigger

Workflows that you will create using NetSuite as trigger or action application, you will have multiple fields to map.

In order to simplify this example, we have chosen a small section of NetSuite attributes to map with the action of "Creating a Lead" in Dynamics app.

• Last Name - Last name of the Lead.
• Mobile Phone - Mobile phone number of a lead.
• Topic - A short name or description to identify a lead. Examples include order, name or the company, or marketing source.
• Budget - The budget that this lead has to spend.
• Description - Any notes that attached to the lead

Figure 1. Data Mapping for NetSuite

From figure 1 we have chosen that when a customer is created in NetSuite we will map that customer's Last Name, Mobile Phone, Company Name, Estimated Budget, and Comments to Microsoft Dynamic's Lead's attributes Last Name, Mobile Phone, Topic, Budget, and Description respectively. You can also mix mapped attributes from the trigger and any text that you type into the text box. We use this to note in the description that the budget is estimated as a quick note. We also use the ROUNDUP excel function to round the budget up, this is just one of many excel functions to choose from.

Example Scenario 2

We have chosen the invoice entity and defined how we want to create an invoice in NetSuite. Most of these configurations can be found while creating an invoice manually in the NetSuite console as well.

With this action, a new invoice is created in NetSuite when a new record is created in Coupa.

Figure 2. Setting up Netsuite action on Connect iPaaS

Create Date

Connect iPaaS allows you to select date of the record creation. For this invoice, Connect iPaaS will mark the current date when it has processed this action. You can select this date to be in the future or in the past.

Invoice Total

Netsuite's Invoice has an attribute for placing the total amount on the invoice. In this case, we mapped the total amount from the invoice in Coupa to the total amount for Netsuite. While this might be overly simple for real world use cases, it does illustrate how easy it is to create data mappings.

Memo

With text box attribute, you can also map data from trigger events in front of text. In this case, Payment notes - is in front of the payment notes data from the Coupa entity.

Tax Details List

Tax Details List is an example of a field that has multiple configurable sub-fields. For some applications like NetSuite and Workday, Connect iPaaS allows to configure these fields which gives you greater control.

Figure 3. Setting up Netsuite's Tax Details on Connect iPaaS

NetSuite Internal ID - Usage

NetSuite uses internal id as an identifier. Internal Ids can be used if you want to update a specific task, contact, or job or want to configure an attribute with something that already exists in NetSuite.

For example, you could modify an existing contact John Downes to have an existing address Reach Research Laboratories.

You can find the internal id of a record from the NetSuite Console as shown in the screenshot below:

Figure 4. Discovering Netsuite's Internal ID

Copy the internal ID and use it while configuring your flow as shown in the screenshot. The internal ID gives a unique connection with the NetSuite record inside Connect iPaaS.

Figure 5. Using Internal ID in RoboMQ's Connect iPaaS