Articles in this section

Debug NetSuite SuiteScript API calls for imports

Gogula R Bhavana

Integrator.io uses NetSuite RESTlets to create and update records in NetSuite. These RESTlets internally rely on SuiteScript APIs (commonly known as nlapi functions) to translate mapped data into NetSuite record objects and submit them. Integrator.io uses an internal framework $R, which converts incoming mapped objects into SuiteScript operations. In some cases, due to NetSuite platform issues, new releases, or customer-specific configurations/customizations, SuiteScript APIs may behave unexpectedly—for example, certain fields may not be applied or errors may differ from expected behavior.

To help identify these issues, integrator.io allows users to enable debugging on the NetSuite-side code and view all underlying nlapi calls executed during the flow. These logs can be copied into a Suitelet for replication, allowing you (or NetSuite Support) to isolate and diagnose the root cause.

How to view native SuiteScript nlapi calls

  1. In integrator.io, for a respective flow's NetSuite import, add a mapping "Print nlapi Debug Logs = true". If the mapping does not appear, refresh the metadata.

  2. In NetSuite, navigate to Customization > Scripting > Scripts > RESTlets, locate the script named Celigo Real-time Import Restlet Runner, and set its deployment logging level to Debug.

    Note

    Remember to revert the deployment logging level to Error once debugging is complete.

  3. In integrator.io, run the respective flow.

  4. In the execution logs, search for either of the following log names:

    1. nlapi call tracked for $R

    2. nlapi calls registered for $R

  5. Copy the nlapi snippets into your own Suitelet and execute them to check whether the issue can be replicated directly within NetSuite.

  6. If the Suitelet,

    1. reproduces the issue: This likely indicates a NetSuite defect or account-specific configuration problem. We recommend contacting NetSuite Support and sharing your standalone script for further analysis.

    2. If the issue is not reproducible in the Suitelet, contact Celigo Support for assistance.

Note

After completing your investigation, remove or disable the Print nlapi Debug Logs mapping. Leaving this active generates unnecessary logging and may impact performance.