SuiteAnalytics 2026.1: NetSuite.com Data Source Retired, JDBC 8.10.184.0, Saved Search Publishing Field Renamed

The 2026.1 SuiteAnalytics notes are short but contain one hard-breaking change for any integration that still talks to the legacy NetSuite.com Connect data source, plus a JDBC security upgrade and a small but script-relevant rename on saved searches.

What changed

1. NetSuite.com Connect data source is gone

As of 2026.1, the legacy NetSuite.com data source is no longer available in SuiteAnalytics Connect. NetSuite2.com is now the only supported data source. Any JDBC/ODBC/ADO.NET connection string, scheduled job, ETL pipeline, Tableau/Power BI workbook, or middleware (Boomi, Celigo, MuleSoft, etc.) still pointed at NetSuite.com will stop returning results once your account is upgraded.

Note that NetSuite2.com uses the Analytics Browser (NS Analytics) schema, which has different table/column naming, different joins, and different data types than the old NetSuite.com (SuiteAnalytics Connect Browser) schema. Queries do not port verbatim — this is a rewrite, not a hostname swap.

2. JDBC Driver 8.10.184.0 recommended

A new JDBC driver build (8.10.184.0) was published on 2025-12-15 containing security fixes. Oracle’s wording is “strongly recommend,” not mandatory, but treat it as required for any production Connect workload. ODBC and ADO.NET drivers are unaffected — no action there.

3. Saved Search publishing flag renamed

The checkbox that exposes a saved search for website publishing has been renamed from Public to Available for publishing on website. The release notes do not state the underlying field ID change, so verify before assuming SuiteScript/SOAP/REST behavior is unchanged. Historically the field was ispublic on the search record; if Oracle has split “public” (visibility/sharing) from “publishable on website” into two distinct fields, any SuiteScript using N/search or SuiteQL referencing ispublic, and any saved-search-permission logic, may need to be re-checked. Confirm the new field internal ID in the Records Browser for 2026.1 before relying on this.

4. AI Summaries (Narrative Insights) for Reports

Generative AI summaries can now be produced for some report results. Gated by account location and user language preference (English only). No scripting surface is described in the release note; this is a UI feature on the report viewer.

5. NetSuite Analytics Warehouse config page updated

The NSAW configuration page has been refreshed. The release note gives no detail beyond that — if you script against or document this page for admins, re-screenshot after upgrade.

What to do

1. Inventory every Connect consumer. Grep configs, .properties files, DSNs, and middleware connection profiles for NetSuite.com. Anything not on NetSuite2.com must be migrated before your account hits 2026.1.
2. Re-test queries against NetSuite2.com. Field names, table names, and joins differ. Pay special attention to custom fields (custbody/custcol/custentity) and to columns that were renamed or split in the NS Analytics schema. See Oracle’s “Changing from NetSuite.com to NetSuite2.com” guide for the mapping.
3. Upgrade JDBC drivers to 8.10.184.0. Download from Home > Settings portlet > Set Up SuiteAnalytics Connect. Roll it out to every host running scheduled jobs, BI tools, or ad-hoc analyst workstations. Restart the consuming service after replacing the JAR.
4. Audit saved searches used by website publishing. Open any saved search currently surfaced via published URL and confirm Available for publishing on website is checked after upgrade. If you provision saved searches via SuiteScript (N/search.create + save) or SOAP/REST and set ispublic: true expecting it to also enable web publishing, verify in the 2026.1 Records Browser whether a separate field (e.g. something like isavailableforpublishing) now controls this, and update your code accordingly.
5. Decide on Narrative Insights rollout. Confirm your account’s region is on the Generative AI availability list and that the target users have language preference set to English; otherwise the AI summary action will not appear.

Caveats

The source release note is light on technical specifics — no field internal IDs, no driver changelog, no list of supported reports for Narrative Insights, and no detail on the NSAW config page changes. Treat the saved-search field rename and any downstream SuiteScript/SuiteTalk impact as verify in a sandbox first.