NetSuite configuration process

The following configuration steps are required in NetSuite prior to leveraging the Parabola integration:

• Create or select a web services only role that can be used by Parabola
• Create or select a user that will be used for the integration in NetSuite. Ensure the role from the step above is applied to this user record
• Create a new integration in Netsuite
• This will result in the creation of your consumer key and consumer secret
• Create a new set of access tokens that reference the user, role, and integration specified above
• This will result in the creation of your token id and token secret

Once complete, you will enter the unique credentials generated in the steps above into the Pull from NetSuite step in Parabola. This will also require your account id, which is obtained from your NetSuite account’s url. Ex: https://ACCOUNTID.app.netsuite.com/

The following document will review how to create each of the items above.

Creating a NetSuite role

The permissions specified on the role applied to your integration will determine which saved searches, transactions, lists, and results you’ll be able to access in Parabola. It is important for you to confirm that the role you plan to use has access to all of the relevant objects as required.

The following permissions are recommended, in addition to any specific transaction/list/report specific you may require.‍

In addition to the below permissions, we also recommend adding the permissions listed in this document.

Transactions

• Any specific transaction types required: sales orders, purchase orders, transfer orders, etc.
• Find transaction

Reports

• Any specific report types required

Lists

• Any specific lists required: items, locations, companies, customers, etc.
• Perform search, persist search, and publish search

Setup

• Log in using Access Tokens
• SOAP Web Services

Custom Records:

• Any specific custom record objects required

Ensure the checkbox for the web services only role is selected.

Creating a NetSuite integration

Video walk-though of the setup process:

‍

Follow the path below in the NetSuite UI to create a new integration record.

1. Setup > Integration > Manage Integrations > New
2. Specify an integration name, ensure the status is set to active, and select the token-based authentication option.
3. Uncheck the TBA: Authorization Role and Authorization Code Grant checkboxes.
4. Save the record.

A consumer key and consumer secret will be generated upon saving the record. Record these items, as they will disappear once you leave this page.

Creating a new access token

Once the role, user, and integration have been created, you’ll need to generate the tokens which are required for authentication in Parabola.

Follow the path below in the NetSuite UI to create a new token record.

1. Setup > Users/Roles > Access Tokens > New Access Tokens
2. Specify the integration created previously, the desired user, and role, and click save.
3. The newly created token id and token secret will appear at the bottom of the page. Record these credentials, as they will disappear once you leave this page.

Configure your settings in Parabola

1. Gather the credentials created from each step earlier in the process and navigate to the Pull from NetSuite step in Parabola.
2. Open the Pull from NetSuite step and click Authorize or Edit Accounts
3. Enter each applicable token and consumer key/secret and click authorize.

Once authorized, you’ll be prompted to select a search type and specific saved search to run. Click refresh and observe your results!

The Return only columns specified in the search checkbox enables a user to determine if all available columns, or only the columns included in the original search, should be returned. This setting is helpful if you’d like to return additional data elements for filtered records without having to update your search in NetSuite.

Helpful Tips

• The Pull from NetSuite step integrates directly with the saved search function. Based on permissions, users have the ability to access all saved searches from the NetSuite UI within Parabola.
• If no saved search options are returned for a specific transaction type, please validate your user and role have access to the specific object you’re attempting to access.
• Users will need permissions within NetSuite to create new integrations, manage access tokens, edit roles, etc. in order to generate the credentials required for this integration
• Formula fields within saved searches will not be returned
• Saved searches which include summary results are not supported
• Ensure the user/role configured for the integration has sufficient permissions to access all necessary saved searches and results

By default, the NetSuite API will only return the full data results from the underlying search record type (item, customer, transaction, etc) and only the internal ids of related record types (vendors, locations, etc) in a search.

For example, running the following search in Parabola would return all of the information as expected from the base record type (item in this scenario), and the internal id of the related object (vendor).

The best way to return additional details from related objects (vendor in this scenario) is by adding joined fields within the search. Multiple joined fields can be added to a single search to return data as necessary.

Alternatively, another solution would be running separate searches and joining the results by using a Combine Tables step within the flow. This is demonstrated below.

Usage notes

• Users will need permissions within NetSuite to create new integrations, manage access tokens, edit roles, etc. in order to generate the credentials required for this integration
• Formula fields within saved searches will not be returned
• Saved searches which include summary results are not supported
• Ensure the user/role configured for the integration has sufficient permissions to access all necessary saved searches and results

Connection

The same credentials and role configured for pulling data from NetSuite can be leveraged within Parabola’s Send to NetSuite step.

One key difference for posting data to NetSuite is ensuring the role has full access to REST Web Services

It also is important to confirm that the role has sufficient permissions enabled to create and/or update the relevant objects that are in scope for your team’s use cases.

This is completed by selecting the relevant permission and updating the access level to Full

As an example, the following permissions need to be enabled for use cases that involve creating & updating sales orders:

• Transactions > Sales Orders > Full Access

Using the step

Creating and updating fields within NetSuite requires providing the internal IDs for relevant objects (items, sales orders, customers, subsidiaries, etc) as opposed to providing the human readable names you’re familiar with (SKUs, order numbers, customer names, etc).

It is a best practice to leverage Pull from NetSuite step or reference file within your flows to gather the internal IDs for reference prior to using the Send to NetSuite step to prevent errors.

Use case example: Creating new sales orders based on a PDF Purchase Order from a customer

Flow inputs:

• An extract from email step that parses a new purchase order PDF from a customer
  • This step extracts the order number, customer name & address, each ordered SKU, the quantity, and the relevant order/ship dates
• Pull from NetSuite steps that list master data references including name and internal ID:
  • Customers
  • Items

Transformation logic:

• Combine the parsed PDF data with the NetSuite reference searches based on the SKU name & Customer Name
• Your dataset should now include the relevant internal ID for each object (Item, Customer, Location)

Flow Outputs:

• Connect your data to a Send to NetSuite step
  • Select the action “Create” and the object “Sales Order”
  • Configure the mandatory fields for entity ID (customer), item internal ID, status, etc.

‍Record statuses

NetSuite requires data to be imported using the specific internal status codes. Specify a status by inserting a custom value with the Status Internal Identifier from the table below.

Bulk Creation

A single flow run can create multiple records within NetSuite. It’s important to leveraging the “grouping” function on the item level mapping to ensure sub-items are consolidated into the relevant parent level record.

An example is grouping sales order items by the sales order number to ensure each item is associated with the corresponding sales order.

Tips:

• Use Pull from NetSuite steps with saved searches for items, customers, vendors, or locations and reference them in flows to look up internal IDs
• The NetSuite Entity field relates to Vendor on POs and Customer on SOs

‍