NetSuite SuiteAnalytics Workbook for Advanced Analytics
A CFO reviewing monthly sales rarely stops at the headline figure. The next questions arrive quickly: which subsidiary drove the variance, which customers, which transactions. A standard report answers the first question well. Each follow-up often needs a different view of the same data, and that is where the time goes.
The delay is widespread. PwC's 3rd SEE CFO Compass Survey, Beyond ERP: Fostering trust in data, systems, and processes (March 2026), found that four in ten companies across eight Southeast European markets are slowed down by long turnaround times for detailed reports. PwC describes the problem as structural, because it limits senior management's ability to monitor expenses at the level of specific units.
This guide is for finance leaders, operations heads and NetSuite administrators who want a clear picture on how to tackle this accurate and real-time reporting issues with SuiteAnalytics Workbook. Let’s understand what SuiteAnalytics Workbook is, how datasets, joins, and linked datasets work, where it sits next to Saved Searches and Reports, and what to plan for before rollout.
What is NetSuite SuiteAnalytics Workbook?
SuiteAnalytics Workbook is an analytics tool inside Oracle NetSuite that brings datasets, table views, pivot tables and charts together in one workspace. Workbook supports multilevel joins across record types, including custom records, and custom formula fields that add dynamic values to an analysis.
Workbook is the most suitable for ad hoc analysis, with instant formula validation, quick data refresh and drill-down through query results. The interface is designed so that users without much record schema or query language knowledge can still build workbooks and datasets through actions such as drag-and-drop. For a finance team, that can shorten the queue of report requests waiting on an administrator every time a question changes shape.
What is the analytics data source, and why does it matter?
The analytics data source is the data layer SuiteAnalytics Workbook uses to expose NetSuite record types, fields and relationships. Oracle NetSuite designed it to present data consistently across the Workbook application, and fields for new NetSuite features have been exposed through it since release 2019.1.
It is not the same source that Saved Searches and Reports use. The location, names and IDs of some fields and record types can differ in the analytics data source, and that some record types and fields, including certain fields with calculated values, have not been ported to it. Recreating an existing Saved Search in Workbook can therefore require different record types, new joins or custom formula fields. It is rarely a one-to-one copy of fields and criteria.
The analytics data source also holds analytical record types that exist only for Workbook. Sales (Invoiced), Sales (Ordered), Manufacturing Component, Manufacturing Transaction and Customer 360 are analytical record types. Each has its own fields and predefined criteria, and combines data from the transaction, transaction line and transaction accounting line record types.
How do datasets and workbooks work together?
SuiteAnalytics Workbook separates two jobs. A dataset defines the data. A workbook defines how that data is analyzed and presented.
Datasets: the data definition
A dataset in SuiteAnalytics Workbook is a query built from a root record type, joined record types, fields, criteria filters and formula fields. One dataset can feed many workbooks and visualizations, so teams can work from a single definition of, for example, open sales orders instead of maintaining several slightly different versions.
That reuse needs governance. Dataset changes update all linked workbooks, which is why recipients of a shared workbook cannot edit the original dataset unless they save their own copy. We recommend treating core datasets the way finance treats a chart of accounts: owned, documented and changed deliberately.
Workbooks: the analysis layer
A workbook holds one or more visualizations built on any dataset the user can access. A visualization can use an existing dataset, a new dataset or two linked datasets. Linked datasets let a team compare metrics from separate datasets in the same pivot table or chart without switching between workbooks.
Table views
Table views show dataset results in rows and columns for record-level review. Users can sort, filter, rename columns and apply conditional formatting, and none of these changes affect the underlying dataset or other visualizations in the workbook. Two documented limits matter in finance work: conditional formatting is not available for DATE fields, and it does not distinguish values in different currencies, so multi-currency figures should be converted to one currency first. Users with the Export Lists permission can export table view data to CSV.
Pivot tables
Pivot tables summarize dataset results across dimensions and measures, such as revenue by subsidiary by period. There is support for multiple fields per dimension, calculated measures, table-specific filters (including Top 10, Bottom 10 and filter by measure), conditional formatting on measures, renamed rows and columns, sorting, and totals and grand totals. Pivot filters change only what the pivot table displays. The dataset itself stays unchanged.
Charts
Workbook charts present dataset results visually so trends and comparisons stand out. A chart can use linked datasets to compare metrics from two datasets in one view, and it is better applying filters to the matching field in each linked dataset, otherwise the chart may show values the user meant to exclude. Charts can be printed or exported as SVG files and added to any NetSuite dashboard through the Analytics portlet.
How does SuiteAnalytics Workbook support business leaders?
Finance teams are relying more on operational data. In Enabling finance insight (July 2026), a global survey of 1,600 finance professionals by ACCA and Chartered Accountants Australia and New Zealand (CA ANZ), more than 60 percent of finance teams said they had increased their use of real-time operational data over the past two years, and 45 percent cited strategic priorities as a key driver of increased data analysis. The table below maps SuiteAnalytics Workbook capabilities to the decisions they support.
Workbook capability | What it enables | Business value |
Reusable datasets | One definition of fields, filters, joins and formulas, reused across visualizations | Every view built on the dataset shows the same numbers, which cuts time spent reconciling competing reports |
Table views, pivot tables and charts | Detailed, summarized and visual views of one dataset | Leaders move from a headline figure to the transactions behind it without requesting a new report |
Linked datasets | Two datasets analyzed together through common keys | Related metrics, such as orders and invoices, compared in one visualization |
Multilevel record joins | Fields from related record types, including custom records, in one dataset | Wider business context in a single analysis |
Calculated measures and custom formula fields | Business-specific calculations on available data | Metrics defined the way the business measures performance |
Analytical record types | Prebuilt record types for sales, manufacturing and Customer 360 analysis | A faster start on common analyses |
Role-based access | Record types and fields shown according to NetSuite role permissions | Governed access to sensitive financial data |
Analytics portlet | Up to 10 Workbook visualizations on NetSuite dashboards | Key metrics in front of decision-makers where they already work |
What is the difference between joining record types and linking datasets?
Combining data correctly is a recognized barrier for finance teams. In the same ACCA and CA ANZ survey, 40 percent of finance professionals named difficulty integrating multiple sources as a key barrier to improving business insight. SuiteAnalytics Workbook offers two distinct ways to bring data together, and choosing the wrong one is a common cause of inaccurate totals.
Joining record types
A record join adds fields from related record types to a single dataset, starting from a root record type and following relationships defined in the analytics data source. Joined results are not aggregated by design, because datasets serve as raw data for visualizations. Depending on the relationship between record types and the join order, results can contain duplicated data. Joining transaction line to a transaction dataset repeats each transaction's total amount once per line, which inflates any totals or grand totals built on that field.
Linking datasets
Linking connects two separate datasets in a workbook and analyzes their results together in a pivot table or chart. Each linked dataset runs as its own background query, and Workbook then aggregates the results based on the common keys, which are fields with the same data type in each dataset. Linked results contain only distinct values from each dataset, so the duplication risk of joins does not apply. A link covers two datasets, and links cannot currently be edited from the Workbook interface.
Aspect | Joining record types | Linking datasets |
Where it happens | Within one dataset | Across two datasets connected to a workbook |
Aggregation | None, by design | Automatic, based on the common keys and where they sit in the visualization |
Duplication risk | Yes, depending on record relationships and join order | No, results contain distinct values from each dataset |
Limit | No fixed limit, though many joins can affect performance | Two datasets per link |
Best for | Fields from directly related records at the same level of detail | Comparing metrics defined in separate datasets or at different levels of detail |
J&J IMPLEMENTATION OBSERVATION
A jewellery manufacturer in India asked us to show piece counts (PCS) next to carat weight (CT) in a single Workbook stock view. Carat weight came from an item-level inventory balance dataset, while piece counts sat in a transaction-level custom record. Bringing both into one tab produced several rows per item and wrong quantity totals.
The fix was to respect the difference in granularity instead of forcing a single view. Checking the grain of each dataset before joining is now one of the first things we do on a Workbook build, because it saves a full rework cycle later.
When should you use Workbook, Saved Searches or Reports?
Each NetSuite reporting tool has a distinct job, and most mature NetSuite accounts use all three. SuiteAnalytics Workbook suits interactive, multi-view analysis. Saved Searches suit targeted record-level queries, reusable criteria, alerts, scheduled emails and dashboard results. Standard Reports suit structured financial and accounting reporting
Tool | Best for | Points to consider |
SuiteAnalytics Workbook | Interactive analysis, pivot tables, charts, linked datasets, dashboard portlets | Runs on the analytics data source, so some fields and record types differ from Saved Searches |
Saved Search | Record-level queries, alerts, scheduled emails, exports, dashboard KPIs | Built for list-style results rather than multi-view visual analysis |
Standard Report | Financial statements, accounting reports, structured business reporting | Built for fixed formats rather than ad hoc exploration |
What should you plan for before rolling out SuiteAnalytics Workbook?
Most Workbook issues we are asked to fix trace back to decisions made before the first visualization was built. We do the following checks before building new reports or moving Saved Searches into Workbook:
- Map the data source. Confirm every required field exists in the analytics data source, and note where a join or custom formula field replaces a Saved Search field.
- Check the grain. Identify one-to-many relationships before joining, and use linked datasets where metrics sit at different levels of detail.
- Define each measure in business terms. Agree whether an amount such as order value includes tax, shipping or discounts before building the formula.
- Set default filters. Agree default date ranges and status filters so large datasets open quickly and show the intended records.
- Govern ownership and access. Name an owner for each shared dataset and review role permissions, since the record types and fields a user sees depend on their NetSuite role.
A few platform points to plan around: SuiteAnalytics Workbook objects are not supported by SuiteBundler, so it is best to keep them out of bundles. Dataset links cover two datasets and cannot be edited in the Workbook interface. Conditional formatting in table views excludes DATE fields and does not separate currencies.
J&J PROCESS NOTE
A North American distribution client asked for a Workbook report that counted sales orders within a value range and date range, with filters any employee could change. NetSuite's Total Amount field included tax and shipping, which was not the order value the business meant. We added a formula field to the dataset (Total Amount minus Tax Total minus Shipping Cost) so the filter matched how the business measured order value.
During testing, the workbook returned a data limit error when opened with no filters on the full order history. That project is why steps three and four of the Readiness Check are standard on our Workbook builds.
How can Jobin & Jismi help you get more from SuiteAnalytics Workbook?
NetSuite SuiteAnalytics Workbook gives finance and operations leaders a governed way to move from transactional data to interactive analysis. Datasets set the data foundation, while table views, pivot tables, charts, joins and linked datasets provide different ways to examine performance. The value depends on how closely the datasets, permissions and visualizations reflect the questions the business actually asks.
Jobin & Jismi, an Oracle NetSuite Solution Provider Partner, helps businesses design datasets, rebuild Saved Searches in Workbook and set up dashboard analytics as part of its NetSuite consulting services and NetSuite customization services. For a wider view of NetSuite analytics options, see our AI-Powered Data Analytics & Reporting with NetSuite Analytics Warehouse (NSAW) blog.
Need to analyze NetSuite data across multiple dimensions without a separate report for every question? Jobin & Jismi can assess and configure SuiteAnalytics Workbook for your reporting needs, from dataset design and record relationships to dashboard visualizations. Speak with our NetSuite experts .
on LinkedIn
Frequently Asked Questions
SuiteAnalytics Workbook is the analytics tool built into Oracle NetSuite for exploring, analyzing and visualizing business data. Users build datasets that define the data, then analyze the results through table views, pivot tables and charts in one workspace. Workbook runs on NetSuite's analytics data source, which Oracle designed to present data consistently across the Workbook application.
SuiteAnalytics Workbook works on two layers. A dataset queries NetSuite records using fields, joins, criteria filters and formula fields, and a workbook presents the dataset results as table views, pivot tables or charts. One dataset can support many visualizations, and two datasets can be linked through common keys to compare their metrics in one pivot table or chart.
A dataset in NetSuite SuiteAnalytics Workbook is a saved query that combines a root record type, joined record types, fields, criteria filters and formula fields to define the data available for analysis. Datasets supply the data for workbook visualizations. Because one dataset can feed several workbooks, dataset changes update every linked workbook.
A dataset defines what data is available, while a workbook defines how that data is analyzed and presented. The dataset holds the fields, joins and criteria that make up the query. The workbook uses the query results to build table views, pivot tables and charts, and a single dataset can be reused across multiple workbooks.
SuiteAnalytics Workbook supports three visualization types: table views, pivot tables and charts. Table views list results in rows and columns, pivot tables summarize data by dimensions and measures, and charts present results graphically. All three can be added to NetSuite dashboards through the Analytics portlet, and a user can add up to 10 Analytics portlets to their dashboards.
Yes. SuiteAnalytics Workbook can link two datasets connected to the same workbook through at least one common key, a field with the same data type in each dataset. Linked datasets are used in pivot tables and charts, and their results are aggregated automatically and contain only distinct values, so they avoid the duplication that record joins can cause.
Yes. Anyone with access to SuiteAnalytics Workbook can share workbooks and datasets with individual users or with roles. Recipients cannot edit the original workbook or dataset, but they can save their own versions, and the record types and fields each person sees depend on the permissions of their NetSuite role.
Inflated totals in SuiteAnalytics Workbook usually come from record joins with a one-to-many relationship. Joining transaction line to a transaction dataset repeats the transaction's total amount once per line, so sums, totals and grand totals built on that field are overstated. Using line-level amount fields, or linking two datasets instead of joining, avoids the problem.
SuiteAnalytics Workbook is not a blanket replacement for Saved Searches. Workbook is stronger for interactive, multi-view analysis, while Saved Searches remain the right tool for record-level queries, alerts and scheduled emails. Because Workbook uses the analytics data source, some Saved Search fields need different record types, joins or formula fields when rebuilt in Workbook.