Custom Tool Scripts Get Execution Log Support and AI Connector Exposure in 2026.1

What Changed

The custom tool script type and its corresponding SDF object definition (toolset) have been updated in 2026.1 with two notable changes:

• Execution log support — Custom tool scripts now support execution logging. Both new and existing custom tools must conform to the updated specification to use this feature. Oracle references SuiteAnswers ID 1024036 for migration details (article title: How to Update Custom Tool Scripts for Execution Log Support in NetSuite 2026.1).
• AI Connector exposure — A new boolean attribute exposetoaiconnector (default F) can be set to T to make a toolset available through the NetSuite AI Connector Service. This is an opt-in flag on the SDF object definition.

SDF Object: toolset

Feature dependency: SERVERSIDESCRIPTING. The SDF XML definition file uses the custtoolset prefix for its scriptid attribute (max 27 characters, lowercase alphanumeric and underscores only).

Required fields:

• name (string) — Display name of the toolset.
• scriptfile (filereference) — Path to the .js script file.
• rpcschema (filereference) — Path to a .json schema file that defines the tool's RPC contract.

Optional fields:

• exposetoaiconnector (boolean) — When T, registers the toolset with the AI Connector Service. Default: F.

The object also supports a permissions structured field for role-level access control.

What to Do

1. Update existing custom tool scripts — Review SuiteAnswers article 1024036 for the specific changes required to enable execution log support. Oracle's source page does not detail the exact modifications; the SuiteAnswers article is the authoritative guide.
2. Re-validate SDF projects — If you deploy custom tools via SDF, ensure your custtoolset XML definitions still validate after 2026.1 lands in your environment. The schema may reject older definitions that lack the updated structure.
3. Evaluate AI Connector exposure — If you are using or planning to use the NetSuite AI Connector Service, set exposetoaiconnector to T on toolsets you want discoverable by AI integrations. Understand the security implications before enabling this on toolsets that perform sensitive operations.
4. Verify in Sandbox first — Test updated custom tool definitions in a sandbox or Release Preview account before 2026.1 reaches production, particularly if you have CI/CD pipelines that deploy SDF bundles containing custtoolset objects.

Gaps in the Source

The release notes page is primarily an SDF object reference, not a detailed change log. The actual breaking changes to the script type for execution log support are gated behind SuiteAnswers ID 1024036, which is not publicly accessible without a NetSuite login. If your environment has custom tool scripts, pulling up that article should be your first step.