SuiteCloud Platform
NetSuite 2026.2
2026-11-13

2026.2 November Monthly Release: N/dataStore Module, Gemini in N/llm, NSAW-to-NSDI Rename, and MCP Expansion

The November 2026.2 monthly release introduces the N/dataStore module for schemaless JSON storage in SuiteScript 2.1, adds Google Gemini models to N/llm, renames NetSuite Analytics Warehouse to NetSuite Data Intelligence, expands MCP access to the Employee Center role, and adds AI client tracking to System Notes.

Affects:SuiteScript 2.1N/dataStoreN/llmREST Web ServicesSuiteTalkSuiteAnalyticsBanking APIMCPODBC DriverSystem Notes

This is the November monthly release for NetSuite 2026.2. Note: these features are rolling out under the NetSuite Next phased availability program — your account may not have them yet.

SuiteScript: New N/dataStore Module

The headline for SuiteScript developers: a brand-new N/dataStore module that provides schemaless JSON document storage directly in SuiteScript 2.1 — no custom records required. You can create, read, update, and delete JSON documents organized into named collections within data stores.

Key details:

  • Storage is scoped: scripts in a SuiteApp share storage isolated from other SuiteApps and from account-scope data. Non-SuiteApp scripts share a single account-scope store.
  • Not supported in SuiteBundler-installed scripts. SuiteApp-only or account-scope only.
  • Do not store sensitive data — Oracle's docs explicitly warn against it, which implies no encryption at rest or field-level access control on stored documents.

This is significant for SuiteApp developers who currently create throw-away custom records just to persist configuration blobs, caching data, or interim processing state. Expect lower governance overhead compared to N/record load/save cycles on custom records, though Oracle has not published governance costs yet — verify before committing to high-volume usage.

SuiteScript: Gemini Models in N/llm

The N/llm module now supports two Google Gemini models:

  • google.gemini-3.8-flash
  • google.gemini-3.1-flash-lite

These are available in llm.generateText(options), llm.generateTextStreamed(options), and their promise-based variants. The model identifiers are under llm.ModelFamily. If you have scripts that hard-code a model enum, you can now branch to Gemini where latency or cost trade-offs favor it.

SuiteAnalytics: NSAW Renamed to NetSuite Data Intelligence (NSDI)

NetSuite Analytics Warehouse (NSAW) is now NetSuite Data Intelligence (NSDI). The Data Warehouse Integrator role is renamed to Data Integrator.

Functional changes beyond the rebrand:

  • Embedded dashboards — NSDI dashboards are viewable directly inside NetSuite at Analytics > NSDI > Dashboards without a separate sign-in. Includes a "My Dashboards" (pinned + recommended) and "All Dashboards" catalog filtered by NSDI permissions.
  • Dataset transfer — You can now push SuiteAnalytics datasets into NSDI from Analytics > NSDI > Data Transfer Setup > SuiteAnalytics Dataset tab. Each transferred dataset creates a corresponding Oracle Analytics Cloud (OAC) workbook in your NSDI instance. Select datasets and individual fields, review mapping, and initiate the transfer.
  • Updated navigation — New left-nav with Configuration, Dashboards, and Resources sections at Analytics > NSDI.

ODBC Driver 9.0.37.0

Available as of November 16, 2026 for Windows. Includes security fixes — Oracle "strongly recommends" upgrading. Download via Home > Settings portlet > Set Up SuiteAnalytics Connect.

Banking: Multi-File Import in a Single Run

The Bank Import API now supports processing multiple bank statement files per import run — up to 100 files per format profile, ordered newest-to-oldest. This requires custom format profiles using connectivity plug-ins that implement the new getTransactionSources() entry point.

Key behaviors:

  • Processing results and errors are tracked per source file.
  • A single run can contain a mix of successful and failed files.
  • Run status reflects completed, partially completed, or failed.
  • Backward-compatible: plug-ins without getTransactionSources() continue through the existing single-file flow.

If you maintain a custom bank import connectivity plug-in, implementing getTransactionSources() opts you in to multi-file mode.

Employee Management & MCP Expansion

MCP Permissions on Employee Center Role

Admins can now grant the Employee Center role access to the NetSuite AI Connector Service (MCP) by setting these permissions to Full:

  • MCP Server Connection
  • Log in using OAuth 2.0 Access Tokens
  • REST Web Services

All three default to None. The Employee Center role's existing record/action restrictions still apply — MCP access is bounded by the role's other permissions.

SuitePeople Goals & Time-Off via REST for MCP

Goals and time-off request records in SuitePeople HR are now exposed through NetSuite REST services, enabling MCP-connected AI assistants to retrieve/update goals, submit time-off requests, and review request statuses. Approval actions are available to authorized managers. All access follows existing role permissions, validation rules, and approval workflows.

SuiteTalk: AI Client Identification in System Notes

The AI Used column in System Notes now captures client information for record changes made via the NetSuite AI Connector Service. The value comes from the request's User-Agent HTTP header and appears as, for example, AI Connector Service (openai-mcp/1.0.0).

Behaviors to note:

  • Applies to both SuiteScript-only MCP tools and SuiteScript-to-REST hybrid tools.
  • Client values are displayed as-is — no mapping to product names.
  • Values with unsupported characters are omitted; long values are truncated with [...].
  • Changes made through the NetSuite UI leave this column empty (unchanged from before).

This is useful for audit trails if multiple AI clients (Claude, ChatGPT, custom agents) are connected to the same account.

Permission Rename: Messages for Analytics and REST

The Messages for Analytics and REST permission is renamed to Search and Query All Company Messages. It now grants access to all company message records via SuiteQL queries and Message saved searches. Non-admin users need both Track Messages and Search and Query All Company Messages permissions to search/query all company messages.

What to Do

  1. N/dataStore: Evaluate whether any existing custom records used purely for JSON/config storage can be migrated. Test governance costs before production use — Oracle has not documented them. Note the SuiteBundler exclusion if you distribute via bundles.
  2. N/llm Gemini models: If you use N/llm, review whether google.gemini-3.8-flash or google.gemini-3.1-flash-lite fits your use case. Update any model selection logic or enums.
  3. NSAW → NSDI rename: Update internal documentation, training materials, and any scripts that reference NSAW by name. The Data Warehouse Integrator role is now Data Integrator — update role references in provisioning scripts or documentation.
  4. ODBC driver: Upgrade to 9.0.37.0 on Windows immediately — security fixes are included.
  5. Bank import plug-ins: If you maintain a custom connectivity plug-in, implement getTransactionSources() to enable multi-file processing. Existing plug-ins continue to work without changes.
  6. MCP / Employee Center: If you want Employee Center users to interact via AI assistants, explicitly grant the three permissions listed above. Review whether the Employee Center role's existing record access is appropriate for MCP-driven interactions.
  7. System Notes auditing: If you have audit or compliance scripts that read System Notes, incorporate the new AI Used column to distinguish AI-originated changes from manual ones.
  8. Permission rename: Search your role configurations and any scripts that reference the old permission name Messages for Analytics and REST. Update to Search and Query All Company Messages. Verify non-admin roles still have both Track Messages and the renamed permission if they need message query access.