Release NotesReference

New SuiteScript 2.1 Execution Preference in NetSuite 2026.1

NetSuite 2026.1 introduces a new preference to execute SuiteScript 2.0 scripts as SuiteScript 2.1, enhancing script compatibility.

·2 min read·NetSuite 2026.1·View Oracle Docs

Starting in NetSuite 2026.1, a significant update allows developers to execute SuiteScript 2.0 scripts as SuiteScript 2.1. This enhancement facilitates smoother transitions and greater compatibility for scripts that were originally written in the 2.0 syntax. This change is part of a broader set of enhancements aimed at improving script execution and integration capabilities in the platform.

Key Features of the Update

  • Preference for Execution: A new configuration option enables the execution of SuiteScript 2.0 scripts under the SuiteScript 2.1 framework, lessening the need for developers to rewrite legacy scripts.
  • Support for PATCH Method: Both N/http and N/https modules now support the PATCH method, which allows developers to make partial updates to records and data.
  • Integration Enhancements: Introduction of a new subtab in the execution log specifically for the AI Connector Service, aimed at aiding integrations.
  • Sandbox Exception Management: Enhanced exception management functionality is now available in sandbox environments.
  • Advanced Reporting Features: New support for consolidated reports and an upgraded SuiteQL tool within the MCP Standard Tools offers enhanced reporting capabilities.

How to Leverage the New Features

  1. Enable Script Execution Preference: Navigate to the preferences section of your account and enable the option to run SuiteScript 2.0 as 2.1.
  2. Update Existing Scripts: For those with existing SuiteScript 2.0 scripts, consider gradually updating them to leverage 2.1 features for better performance and capabilities.
  3. Utilize Logging Features: Make use of the new logging capabilities for custom tool scripts to diagnose and troubleshoot issues efficiently, ensuring you add necessary JSDoc tags and define entry points correctly.

Who This Affects

  • Developers: Especially those maintaining or developing custom scripts.
  • Administrators: Administrators managing the NetSuite environment will find it crucial to configure these new settings.
  • Integration Specialists: Those working with API and integration services may need to update their integration scripts accordingly.

Key Takeaways

  • The NetSuite 2026.1 update introduces a critical new preference for executing SuiteScript 2.0 scripts as SuiteScript 2.1.
  • Improved support for HTTP methods, including PATCH.
  • Enhanced debugging and logging capabilities for custom tool scripts.
  • New functionalities that promote better integration and exception management in sandbox accounts.

Frequently Asked Questions (4)

What steps are involved in enabling SuiteScript 2.0 scripts to run as 2.1 in NetSuite 2026.1?
To enable this option, you need to navigate to the preferences section of your account and activate the setting that allows SuiteScript 2.0 scripts to be executed as SuiteScript 2.1.
Does the new SuiteScript 2.1 execution preference require rewriting existing SuiteScript 2.0?
No, the preference reduces the need to rewrite legacy SuiteScript 2.0 scripts, but developers can gradually update scripts to fully leverage SuiteScript 2.1 features.
How does support for the PATCH method in NetSuite 2026.1 affect integration scripts?
With the support for the PATCH method in `N/http` and `N/https` modules, developers can now make partial updates to records, enhancing the flexibility of integration scripts.
What new functionalities are available in the sandbox environment with NetSuite 2026.1?
The update introduces enhanced exception management functionality specifically for sandbox environments, improving testing and development processes.

Weekly Update History (1)

Release Notesupdated

Updated link to the PDF file to point to v11. For the latest version, see NetSuite 2025.2 Release Notes.

View Oracle Docs
Source: New in February Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?