Release NotesReference

New SuiteScript 2.1 Execution Preference in NetSuite 2026.1

New in NetSuite 2026.1, SuiteScript 2.1 allows execution of 2.0 scripts, enhancing flexibility and performance.

·3 min read·NetSuite 2026.1·View Oracle Docs

Starting in NetSuite 2026.1, several key enhancements have been introduced that significantly expand the capabilities of SuiteScript and integration tools. These updates are designed to streamline development processes, enhance the flexibility of script execution, and improve overall usability for developers and administrators.

What's New in NetSuite 2026.1?

New Preference to Execute SuiteScript 2.0 Scripts as SuiteScript 2.1

One of the major updates is the new preference that allows SuiteScript 2.0 scripts to be executed as SuiteScript 2.1. This opens the door for developers working with existing scripts to leverage the improved features and performance benefits of the 2.1 version without extensive rewrites.

Support for PATCH Method in N/http and N/https

The N/http and N/https modules now support the PATCH method, which is essential for modifying existing resources on a server without sending the entire resource.

SuiteProcurement Enhancements

Recent improvements in the SuiteProcurement area enhance transactional efficiency and tracking for procurement processes, although specifics of these enhancements require further exploration in subsequent documentation.

Subscription Metrics Cohort Enhancement

The addition of an acquisition date field on customer records allows businesses to analyze customer acquisition more effectively, informing marketing strategies and customer relationship management activities.

Integration Logs for AI Connector Service

A new subtab in the execution logs of integration records for the AI Connector Service has been implemented. This provides developers with enhanced visibility, enabling better monitoring and troubleshooting of integrations powered by AI.

Exception Management in Sandbox Accounts

This update now supports exception management within Sandbox accounts, allowing for better testing and debugging of scripts and integrations before deployment into production environments.

Updated CDL Role Restrictions

Class, Department, and Location (CDL) role restrictions on account records have been updated to include unassigned values, enhancing reporting and data visibility based on your organizational structure.

Support for the GPT-OSS Model in N/llm Module

Support for the GPT-OSS model in the N/llm module further enhances the capabilities for natural language processing and AI-driven functionalities within NetSuite.

Advanced Intercompany Journal Entries

Improvements to the handling of advanced intercompany journal entries have been made to support Philippine tax audit files better, streamlining compliance and reporting.

Support for Consolidated Reports and New SuiteQL Tool

The introduction of consolidated reporting capabilities and a new SuiteQL tool within the MCP (Multi-Channel Platform) standard tools allow for more sophisticated data queries and reporting within NetSuite, improving decision-making and business insights.

Who This Affects

  • Developers: Benefit from enhanced scripting capabilities and performance improvements.
  • Administrators: Gain new tools for managing user roles and logging execution for troubleshooting.
  • Business Analysts: Leverage new metrics and reporting tools to inform strategies and decisions.

Key Takeaways

  • New preferences in SuiteScript 2.1 enhance execution flexibility for 2.0 scripts.
  • The addition of PATCH method support facilitates more efficient API integrations.
  • Improved tools for monitoring and troubleshooting increases overall development productivity.
  • Enhanced reporting tools allow for better data insights and strategic decision-making.

Weekly Update History (1)

Release Notesupdated

Updated link to the PDF file to point to v23. 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?