Enhanced Logging for Custom Tools in NetSuite 2026.1

Enhanced logging for custom tools in NetSuite 2026.1 improves script monitoring. Learn key updates for custom tool scripts.

·2 min read·6 views·NetSuite 2026.1·From NetSuite Release Notes PDF

As of NetSuite 2026.1, developers can leverage an enhanced logging feature for custom tool scripts, significantly improving script monitoring and troubleshooting. This article outlines how to update existing custom tool scripts and their associated SuiteCloud Development Framework (SDF) objects to take advantage of these capabilities.

Updates for Custom Tool Scripts

To ensure your custom tool scripts benefit from enhanced execution logs, implement the following updates:

JSDoc Tag Addition

  • Add the JSDoc tag @NScriptType CustomTool to your custom tool script. This tag informs NetSuite that your script should be treated as a custom tool, enabling the new logging features associated with this script type.

Asynchronous Entry Points

  • Declare entry point functions as asynchronous. By marking your methods with the async keyword, you enhance their ability to handle operations that require waiting for resources, such as API calls, thus yielding better script performance and log accuracy.

Updates for SDF Object XML Definitions

In addition to script modifications, adjustments are necessary for the corresponding SDF object XML definition files:

  • Rename the object from tool to toolset. This change aligns object nomenclature with functionality improvements introduced in the new version.
  • Change the script ID prefix from customtool_ to custtoolset_. Maintaining proper naming conventions ensures clarity and consistency across your development projects.
  • Rename the attribute exposeto3rdpartyagents to exposetoaiconnector. This change reflects the enhanced connectivity options available for integrations with external systems.

Key Takeaways

  • Implement the @NScriptType CustomTool tag to activate logging features for your scripts.
  • Declare entry point methods as asynchronous for optimal script functionality.
  • Update SDF object names and prefixes to maintain compatibility with the latest enhancements.
  • Renaming the exposeto attributes helps clarify their purpose in the context of integrations.

By applying these updates, NetSuite developers can maximize their ability to monitor script execution and troubleshoot issues efficiently, aiding in delivering robust custom tool functionalities. For more detailed guidance on updating your custom tools, refer to the documentation on updating custom tools.

Frequently Asked Questions (4)

Does the enhanced logging feature apply to all custom tool scripts in NetSuite 2026.1?
Yes, the enhanced logging feature applies to all custom tool scripts in NetSuite 2026.1 as long as they include the required JSDoc tag @NScriptType CustomTool.
What permissions are required to implement the enhanced logging features?
The article does not specify particular permissions required to implement the enhanced logging features, but typically, a developer role with access to script management is needed.
How do the changes to SDF object XML definitions affect existing custom tools?
Existing custom tools will need modifications to their SDF object XML definition files, specifically renaming objects and changing prefixes to align with the enhancements introduced in 2026.1.
What happens if I don't declare entry point functions as asynchronous?
If entry point functions are not declared as asynchronous, the script performance and log accuracy may be negatively impacted, which could lead to issues in monitoring and troubleshooting.
Source: Enhanced Logging for Custom Tools in NetSuite 2026.1 NetSuite Release Notes PDF. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

More in SuiteScript

View all SuiteScript articles →

Also from NetSuite 2026.1

View all NetSuite 2026.1 changes →