Custom Tool Script Objects in NetSuite 2026.1

TL;DR Opening

Starting in NetSuite 2026.1, the introduction of custom tool script objects provides developers the ability to create and manage tool scripts effectively, referencing both script files and JSON schema files in a structured format. This enhancement simplifies the integration process, making it easier to manage tools within the SuiteCloud Development Framework.

What's New

The new custom tool script object feature allows developers to define and configure their custom tools using XML file definitions. For instance, the example provided in the documentation illustrates how to set up a tool named Report Tool, linking it to a JavaScript file and a JSON schema file.

Example of a Custom Tool Script Object

Here’s a closer look at the Report Tool custom tool object definition:

<toolset scriptid="custtoolset_reports">
  <name>Report Tool</name>
  <scriptfile>[/SuiteApps/com.netsuite.tools/tools/report.js]</scriptfile>
  <rpcschema>[/SuiteApps/com.netsuite.tools/tools/report_schema.json]</rpcschema>
  <exposetoaiconnector>T</exposetoaiconnector>
  <permissions>
    <permission>
      <permkey>LIST_EMAILTEMPLATE</permkey>
      <permlevel>FULL</permlevel>
    </permission>
    <permission>
      <permkey>ADMI_CRMLIST</permkey>
      <permlevel>VIEW</permlevel>
    </permission>
  </permissions>
</toolset>

Key Features Explained

Script ID: Each toolset is identified by a scriptid, allowing for easy referencing.
Script File: The scriptfile tag points to the JavaScript file, containing the functional logic.
JSON Schema: The rpcschema tag specifies the location of the schema file that outlines the expected structure and validation rules.
Exposure to AI Connector: The exposetoaiconnector tag indicates whether or not the tool is accessible via AI integration connectors.
Permissions: The permissions section defines access levels for various key permissions, allowing for customized user access control.

Who This Affects

This update impacts several roles within the NetSuite ecosystem:

Developers: Who will benefit from enhanced tool creation capabilities.
Administrators: Responsible for managing custom tool objects and permissions.
Integrators: Utilizing AI connectors will find this useful for implementing integrations with external systems.

Key Takeaways

Custom tool script objects introduced in NetSuite 2026.1 simplify developer workflows.
Tool definitions are now structured in XML, which enhances readability and management.
Each tool can have specified permissions for different roles, improving security and access control.
The ability to reference JavaScript and JSON files together streamlines the integration of functionalities.
This enhancement opens avenues for better customization and integration within the SuiteCloud Development Framework.

Frequently Asked Questions (4)

What permissions are required to manage custom tool script objects in NetSuite 2026.1?

Permissions are defined within the XML configuration of the custom tool script object. For example, the 'Report Tool' includes permissions such as 'LIST_EMAILTEMPLATE' with full access and 'ADMI_CRMLIST' with view access.

Do I need to use XML to define custom tool script objects in NetSuite 2026.1?

Yes, custom tool script objects in NetSuite 2026.1 are defined using XML file definitions, which organize references to script files and JSON schema files.

How can I expose a custom tool script object to an AI integration connector in NetSuite 2026.1?

To expose a tool to an AI connector, you need to set the 'exposetoaiconnector' tag to 'T' in the toolset XML definition, ensuring it is accessible for AI integrations.

Is it possible to reference both JavaScript and JSON schema files in a single custom tool script object?

Yes, in NetSuite 2026.1, you can reference both script files through the 'scriptfile' tag and JSON schema files through the 'rpcschema' tag within a single custom tool script object's XML definition.