NetSuite SuiteAnalytics Workbook Tutorial: How to Build Better Reports

Build a Report Your Team Can Check

A useful report answers one clear question. For this tutorial, use: “Which items have the most sales-order quantity, and what is their order status?” You will build a dataset, summarize it in a pivot, and add a chart that makes the result easier to read.

We conducted a documentation review of Oracle’s Workbook guidance and independent chart-design standards to shape this walkthrough. The example is a suggested practice exercise, not a claim of testing in a customer account. Field access and available records depend on your account setup.

Understand the Dataset and Workbook

Oracle describes two separate parts: the dataset selects fields and filters; the workbook presents those results as tables, pivots, and charts. A dataset can support several workbooks, and changes to it flow through to those views.^[1] Think of the dataset as your agreed source and the workbook as the way you explain it.

For this first exercise, keep the scope small. Use one date range and a few known orders. Add more detail after you can explain every row.

1. Set Your Question and Check Access

Open the Analytics tab. Before creating anything, agree on what the report will count. Our example measures ordered quantity by item and status. It does not measure recognized revenue or remaining units to ship.

• Choose a fixed start and end date for the first review.
• List the order statuses you want to include.
• Keep quantities in comparable units, especially when comparing different items.
• Choose several known sales orders to use as a check.

Oracle states that available records and fields depend on enabled features and your role permissions. If a needed record is missing, ask your administrator to check that access.^[2] Do the final review using the role that will read the report.

2. Create a Small Dataset

From Analytics, open Workbooks > New Workbook > New Dataset. Oracle documents this route for building a workbook and its source together.^[3] Select the Sales (Ordered) record type for this exercise. If your role does not show it, resolve that with your administrator before continuing.

Review the fields already in the Data Grid. Keep Item and Quantity for the core report. Add the related Transaction record’s Status field. Retain a transaction identifier and date for checking the detail. Oracle’s field guide explains that fields must be in the grid to be used in workbook views; adding a related record’s field creates a join.^[4]

3. Filter and Inspect the Rows

Add your selected date range and status rules in the dataset criteria area. Preview the results. Find one known order and compare its item rows and quantities with the source record. Then repeat the check for an order with several lines.

Write the scope in the dataset description. For example: “Ordered quantity by item for August 2026; includes the listed order statuses.” Avoid calling the result “open demand” unless your fields and rules actually measure the quantity still needed.

Oracle warns that record joins can duplicate data, depending on the relationships and join order.^[6] Our analysis puts row checks before charts for this reason. If an order total appears on three item rows, adding it three times will overstate the result. Use a measure that belongs to the level of detail you are reporting.

Your Workbook Build Flow

Use this five-step flow for future reports too. Return to the row check whenever you add a join or change a measure.

4. Build a Pivot Table

Choose Apply to workbook and select a pivot visualization. In the Layout panel, place Item and Status in Rows. Place Quantity in Measures, set its summary type to Sum, and refresh. This follows the quantity portion of Oracle’s pivot tutorial.^[5]

Start with quantity so you can review one measure at a time. If you later add Amount (Net), define the currency basis first. Oracle says values in different currencies need conversion to one currency before arithmetic. Also, a filter applied to a pivot affects that pivot, not its source dataset or the other views.

As a simple practice check, imagine two included lines for the same item and status: 3 units and 5 units. The pivot should show 8. This is an illustrative calculation. Compare your actual results with your chosen orders before relying on the report.

5. Add a Chart With a Clear Point

Add a chart visualization using the same dataset. For a first view, put Item on the category axis and summed Quantity in Measures. Use a bar chart to compare items. Keep the date and status scope aligned with the pivot, and title it clearly: “Ordered quantity by item — August 2026.”

The UK Government Analysis Function recommends bar charts for comparing categories and line charts for time series.^[7] A time trend is a useful next step once you add the relevant date field and grouping. Keep the first chart focused on one question.

When you share a chart in a document or web page, include its main finding in text and provide the underlying values. W3C guidance calls for text alternatives that explain the information in complex images such as charts.^[8] This also gives readers a way to check exact numbers.

6. Save, Share, and Review

Use a name such as “Sales Orders — Quantity by Item and Status.” Record the date rules, included statuses, quantity definition, and owner in the description. Save the dataset changes, then save the workbook. Oracle requires datasets used by workbook visualizations to be saved before the workbook can be saved. Use Share to select the intended users or roles.

Ask one reader to open the shared workbook with their usual role. Compare their result with the expected scope. Record any differences before the team uses the report in a meeting.

• Check a known order and a multi-line order against the source.
• Confirm the date window and status rules in every view.
• Check that Sum is used for quantities you intend to add.
• Review the chart title, units, and any currency labels.
• Name the person who will review future dataset changes.

Fix the Cause When Results Look Wrong

If totals rise after adding a field, remove the new join temporarily and compare the detail. If the pivot and chart disagree, compare their filters and summaries. If a reader cannot find a field, check role access before rebuilding the report.

Keep the first version small enough to explain. A checked dataset, a useful pivot, and one clear chart give your team a sound starting point. Expand the workbook only when the next field answers a real business question.

References

1. Oracle NetSuite: Custom Workbooks and Datasets.
2. Oracle NetSuite: Accessing and Sharing Workbooks and Datasets.
3. Oracle NetSuite: Creating a Workbook Using a New Dataset.
4. Oracle NetSuite: Add Fields and Join Record Types.
5. Oracle NetSuite: Pivot Your Dataset Query Results.
6. Oracle NetSuite: Joining Record Types Versus Linking Datasets.
7. UK Government Analysis Function: Data Visualisation — Charts.
8. W3C Web Accessibility Initiative: Complex Images.