NetSuite SuiteAnalytics: Workbooks, Queries, and Dashboards Explained

A NetSuite SuiteAnalytics workbook gives finance teams, operations managers, and administrators a structured way to query, pivot, and visualize business data without exporting to spreadsheets or writing custom scripts. SuiteAnalytics is the umbrella term for four interconnected tools: Workbooks, Datasets, SuiteAnalytics Connect (ODBC/JDBC), and Analytics Portlets. Together they replace the fragmented approach of using saved searches plus manual Excel pivots with a governed, in-platform analytics layer. This guide covers how each component works, how they compare to saved searches, and which scenarios call for which tool. For a broader look at NetSuite reporting and dashboards, including KPI tiles and classic report writers, that context sets the stage for understanding where SuiteAnalytics fits.

What Is SuiteAnalytics? The Full Toolset Explained

SuiteAnalytics shipped with NetSuite 2019.1 and has expanded with every subsequent release. The architecture separates data definition from data presentation, which is a meaningful change from the all-in-one saved search model. Oracle’s official SuiteAnalytics documentation covers the full feature set as it evolves with each release.

• Datasets define which record types, fields, joins, and filter conditions form the base of an analysis. Think of a dataset as a reusable view of the database that multiple workbooks can reference.
• Workbooks consume a dataset and let users build pivot tables, tabular views, and charts inside the NetSuite UI. A single workbook can contain multiple visualization sheets.
• SuiteAnalytics Connect exposes NetSuite data over a standards-compliant ODBC or JDBC connection. External BI tools (Tableau, Power BI, Looker) query NetSuite as if it were a relational database.
• Analytics Portlets embed workbook charts directly onto NetSuite dashboards, making workbook output visible at the role or center level without requiring users to open the workbook manually.

Classic saved searches remain available and are still the right tool for operational tasks like filtered record lists, email alerts, and workflow conditions. SuiteAnalytics adds an analytical layer on top, designed for aggregation, comparison, and trend work rather than row-level record retrieval.

SuiteAnalytics Workbooks: Datasets, Pivot Tables, and Charts

A netsuite suiteanalytics workbook is composed of three layers: the dataset, one or more pivot or tabular views, and optional chart sheets. Each layer is configurable independently, so changing the chart type does not affect the underlying query logic.

Datasets

Datasets support multi-record-type joins similar to saved searches but with a more explicit join path editor. You select a root record type (for example, Transaction), add related record joins (Subsidiary, Item, Sales Rep), and then choose the specific fields to expose. Filter criteria can be applied at the dataset level, at the workbook view level, or at both. Dataset-level filters restrict the data available to any view; view-level filters narrow further without altering the shared dataset.

One important constraint: datasets do not support formula fields in the same way saved searches do. Complex calculated columns require either SuiteScript population of a custom field or a SQL-level calculation through Connect. This is a known gap for teams that rely heavily on formula-based saved searches.

Pivot Tables

Workbook pivot tables follow the row/column/measure model. You drag fields into row dimensions (for example, Subsidiary, Period), column dimensions (Quarter, Year), and measure slots (Amount, Quantity). NetSuite aggregates automatically using sum, count, average, min, or max. Cross-dimensional percentages and running totals are available through the measure configuration panel.

A netsuite pivot table workbook can reference up to 10 row dimensions and 5 column dimensions, though performance degrades visibly beyond 3-4 dimensions on large datasets. For high-cardinality analyses, filtering at the dataset level to a single subsidiary or date range before pivoting is standard practice.

Charts

Each chart sheet in a workbook pulls from one pivot or tabular view. Supported chart types include bar, line, area, scatter, and donut. Charts update when the underlying view’s filters change, making them suitable for parameterized reporting where users adjust period filters on the fly.

How to Build a NetSuite SuiteAnalytics Workbook Step by Step

The following sequence creates a revenue-by-subsidiary workbook from scratch. Permissions required: Analytics Workbook (Full) role permission under Reports.

1. Create the dataset. Navigate to Analytics > Datasets > New. Set the root record type to Transaction. Add a filter: Type = Invoice. Join the Subsidiary record type and pull in Subsidiary Name. Select Amount (Transaction Currency), Close Date, and Sales Rep fields.
2. Save the dataset with a descriptive name such as “Invoice Revenue Base.” Published datasets are visible to all roles with Analytics access; private datasets are visible only to the creator.
3. Create the workbook. Navigate to Analytics > Workbooks > New. Select your saved dataset. NetSuite opens the workbook editor with a blank pivot view.
4. Configure the pivot. Drag Subsidiary Name to the Rows area. Drag Accounting Period to the Columns area. Drag Amount to the Values area and set aggregation to Sum.
5. Add a view-level filter. Set Close Date between the current fiscal year start and today. This restricts the view without modifying the shared dataset.
6. Add a chart sheet. Click the “+” tab at the bottom of the workbook. Select Chart. Choose the pivot view as the source. Set chart type to Bar and select Subsidiary as the category axis.
7. Save and share. Use the Share button to grant access by role or individual user. Charts from this workbook can now be added to dashboards as Analytics Portlets.

SuiteAnalytics Connect: SQL Access via ODBC and JDBC

SuiteAnalytics Connect is a separate licensed feature that exposes NetSuite data through a standards-compliant endpoint. Users connect from any SQL client or BI tool using a NetSuite-provided ODBC or JDBC driver.

Connection Setup

Download the driver from the NetSuite support portal. Oracle’s SuiteAnalytics Connect setup guide covers driver versions, supported authentication methods, and known compatibility notes. Connection parameters include Account ID, Role ID, and either token-based authentication (TBA) or username/password. The driver maps NetSuite record types to virtual tables. For example, the transaction virtual table contains header-level fields from all transaction types, while transactionline contains line-level detail.

What You Can Query

Connect exposes over 200 virtual tables covering transactions, items, customers, vendors, employees, projects, and subsidiary structures. It does not expose all custom record data by default; custom tables appear if the administrator enables them under Setup > SuiteAnalytics Connect > Schema Browser.

SQL dialect support is ANSI-compatible with some limitations: no stored procedures, no DDL, and read-only access. Aggregation functions (SUM, COUNT, AVG, GROUP BY) work as expected. Window functions are partially supported depending on the driver version.

BI Tool Integration Pattern

A typical integration connects Tableau or Power BI directly to Connect using the JDBC driver, schedules a nightly extract of transaction data into a staging schema, and builds the BI layer on top of the staging data rather than live queries. Live queries through Connect are possible but carry latency costs on large record sets. For organizations managing NetSuite financial reporting across multiple subsidiaries, staging-based extraction is the more reliable pattern.

Building KPI Dashboards with Analytics Portlets

Analytics Portlets bridge the gap between workbook analysis and the NetSuite dashboard experience. Once a workbook chart is saved and shared, it becomes available as a portlet that any user with the right role can add to their dashboard.

Adding an Analytics Portlet

1. Open the target dashboard (Home or a Center tab).
2. Click Personalize Dashboard (top-right gear icon).
3. In the Add Content panel, expand the Analytics section.
4. Select the workbook chart by name and drag it to a column.
5. The portlet renders the chart at dashboard load and respects any view-level filters defined in the workbook.

Role-Based Dashboard Configuration

Administrators can publish a standard dashboard layout to a role using Setup > Company > Publish Dashboard. When a role receives a published dashboard, its Analytics Portlets are pre-populated with the charts the administrator defined. Individual users can then personalize further within that structure. This pattern is common for finance close dashboards where the CFO and controllers need identical KPI visibility without configuring their own portlets.

Portlet Refresh and Caching

Analytics Portlets refresh on dashboard load. NetSuite applies result caching at the dataset query level, typically with a 20-minute cache window. For near-real-time KPIs, the standard portlets (Summary, Trend Graph) connected to saved searches update more frequently. For executive-level daily reporting, the 20-minute window is generally acceptable. Understanding this distinction matters for teams building NetSuite financial management workflows that require consistent, role-appropriate data visibility.

NetSuite Workbooks vs Saved Searches: When to Use Each

The netsuite workbooks vs saved searches question comes up in almost every SuiteAnalytics implementation. The two tools have different strengths and the choice depends on the specific task.

Migration Approach

Teams moving from saved searches to workbooks typically start by identifying saved searches used purely for pivot or chart output rather than operational record retrieval. Those are the clearest migration candidates. Searches that feed workflow conditions, scheduled emails, or SuiteScript stay as saved searches. A practical migration sequence: rebuild the dataset to match the search’s join structure, confirm row counts match, rebuild the pivot, then retire the search.

One limitation to communicate to users: workbooks do not appear in the global search or Quick Links bar the way saved searches do. Users access them through the Analytics menu or via portlets. Adoption training needs to address this navigation change explicitly.

Real-World Use Cases Across Finance, Operations, and Projects

Finance Close Reporting

A common workbook configuration during month-end close tracks invoice-to-cash by subsidiary. The dataset joins Transaction, Subsidiary, and Customer records. The pivot rows show subsidiary, columns show aging bucket (0-30, 31-60, 61-90, 90+), and the measure is open amount. Finance managers filter by accounting period and run the workbook at day 3, 5, and 10 of close to track collection progress. The same workbook feeds an Analytics Portlet on the Controller’s dashboard.

Inventory Turns Analysis

An inventory turns workbook uses the Item record as root, joined to Inventory Detail and Transaction Line. The pivot calculates average inventory value in rows and COGS in a parallel tabular view. Turns = COGS / Average Inventory is computed outside NetSuite (in Excel or a BI tool via Connect) because workbooks do not support cross-view formula calculation. The workbook provides the source figures; the calculation layer sits downstream.

Revenue Pipeline Tracking

Sales operations teams build pipeline workbooks from the Opportunity record type. The dataset filters on Status not equal to Closed Lost. The pivot shows Sales Rep in rows, Expected Close Month in columns, and Weighted Amount as the measure. Charts visualize the pipeline by stage and quarter. This workbook replaces three separate saved searches that sales managers previously ran and manually combined in a spreadsheet.

Project Profitability

Professional services firms using NetSuite’s Project module build workbooks joining Project, Project Task, Time Entry, and Expense Report records. The pivot compares budgeted hours and cost against actual hours and cost by project and phase. Margin percentage requires a Connect-based query or a custom field because the workbook pivot engine does not support derived ratio calculations natively. Teams that identify this limitation early plan the Connect integration before go-live rather than retrofitting it later. Aaxonix’s NetSuite implementation and analytics services help project-driven businesses configure this architecture correctly from the start.

SuiteAnalytics represents a meaningful step forward from the saved search-only approach, but it works best when teams understand which tool fits which task. Workbooks handle pivot analysis and chart-based reporting well. Saved searches handle operational retrieval, workflow triggers, and formula-heavy calculations better. Connect fills the gap for external BI integration. Aligning each reporting requirement to the right component before building reduces the redesign cycles that slow down NetSuite analytics programs and keeps dashboard data reliable for the teams that depend on it.