NetSuite connector FAQs

Q1: My existing NetSuite connection appears offline despite having correct credentials for authentication. What could be the reason?

A: If your NetSuite connection appears offline despite having correct credentials, you might have used the basic authentication type for creating the connection and you may also have enabled 2FA in NetSuite. To enable such a connection, first disable 2FA in NetSuite and enter the credentials again to create the connection. However, if you do want to use 2FA in NetSuite, you must modify your Authentication type from Basic to Token.

Q2: Is there any way to use basic authentication type with 2FA in NetSuite?

A: It is highly recommended that you switch your connection’s Basic authentication type to the Token authentication type. However, if you still want to use basic auth type, you can create a custom role in NetSuite specifically for integrations with all of the required permissions and 2FA disabled.

Q3: Do I need an integrator.io sandbox license to a connection to a NetSuite sandbox environment?

A: If you are building a custom integration, then you can create an integrator.io connection to the NetSuite sandbox environment without purchasing an integrator.io sandbox license. You can specify the Environment setting of the NetSuite connection.

Integration App environment licensing requirements:

• Production environment license: Integration Apps require an integrator.io production environment license to connect to a NetSuite production environment.
• Sandbox environment license: Integration Apps require an integrator.io sandbox environment license to connect a NetSuite sandbox environment.

Note: Although it is technically possible to connect the NetSuite sandbox environment to your integrator.io production environment with an Integration App production license, Celigo strongly recommends that you purchase the Integration App sandbox license. It allows you to use the integrator.io sandbox environment to connect the NetSuite sandbox environment and perform all testing in sandbox environments. If you choose to use your Integration App production license to connect to a NetSuite sandbox environment, you must uninstall your Integration App after you are done with testing and then reinstall and reconfigure the Integration App to connect to production environments.

Q4: Why am I getting errors in integrator.io when I try to create imports or exports with a POST request?

A: When connecting to NetSuite with a POST request, you must include the requestLevelCredentials field and set it to TRUE in the request. If this field is not included in your request, the setting defaults to FALSE, and your request will be unsuccessful.

Q5: Do dynamic lookups behave the same way for SuiteApp SuiteScript 2.0 and SuiteBundle? This applies to the How can we find existing records lookup and dynamic lookups in mappings.

A: The SuiteApp SuiteScript 2.0 version differs from the SuiteApp SuiteScript 1.0 and SuiteBundle versions regarding lookups. In SuiteApp 2.0, lookups are first submitted, then evaluated, and finally, a second call is made to submit the record. This helps overcome the issue of governance points. If you’re working with a lot of data and need to run a lookup for each line of data, it’s best to use SuiteScript 2.0.

Note that the How can we find existing records lookup and dynamic lookups in mappings are the same type of lookup. integrator.io will group these requests and call the RESTlet once. However, if you have more than 400 lookups, they’ll be divided into 400 lookup packets in each request. This helps save governance limit points and not exceed the limit.

For example, let’s say you’re submitting 10 records with 10 line items each in your import. For each line item (of which there are 10), you’re submitting 4 dynamic lookups for a total of 40 dynamic lookups per line item. For each record, you’re submitting one How can we find existing records lookup. This means you’re submitting 41 lookups for each record. Now, if you multiply the 41 total lookups for each record by 10 (total records), you’re submitting a total of 410 lookups for your import.

As mentioned above, if you have more than 400 lookups, they’ll be divided into 400 lookup packets for each request. Therefore, you’d have one request with 400 lookups and a second request with 10.