SuiteAnalytics Workbook vs. Saved Searches: Which to Use for NetSuite Reporting
A guide for live NetSuite accounts choosing between saved searches, SuiteAnalytics Workbook, and SuiteQL for operational dashboards, finance analysis, and complex reporting.
Building custom NetSuite reports and not sure which approach fits? Tell us what your account needs to show.
NetSuite-Certified · Post-go-live specialist · Sandbox-first development · Month-to-month
Quick answer
Saved searches and SuiteAnalytics Workbook are both built into NetSuite and both produce reports, but they serve different use cases. Saved searches are available on all NetSuite editions. They run in real time against live data, support formula columns and summary groupings, can be embedded in dashboard portlets, and can trigger workflow conditions and alerts. For operational reporting and anything embedded in the platform, saved searches are the right tool. SuiteAnalytics Workbook is a more modern interface with pivot tables, charting, and exploratory data analysis. It is better suited for ad-hoc analysis and trend exploration but is not available on every NetSuite edition and cannot be embedded in workflow conditions or used as dashboard portlets the way saved searches can. SuiteQL is a third option for the most complex joins, but it requires developer time because it runs only through a script. Most live NetSuite accounts rely on saved searches for operations and use Workbook for finance team analysis when their edition includes it.
Saved searches vs. Workbook vs. SuiteQL: capability comparison
The table below maps capabilities across all three reporting tools. Most accounts use saved searches for daily operations and Workbook for finance analysis when the module is available.
| Capability | Saved search | Workbook | SuiteQL |
|---|---|---|---|
| Setup method | UI-based, no code | UI-based, no code | Developer required (script) |
| Pivot tables | No | Yes | No (output only) |
| Charts | Limited (portlet charts) | Yes (built-in charting) | No |
| Dashboard embedding | Yes (portlets) | Limited | Via Suitelet only |
| Workflow conditions | Yes | No | No |
| Edition availability | All editions | SuiteAnalytics module required | All editions (via script) |
| Real-time updates | Yes | Yes | Yes (when script runs) |
| Developer required | No | No | Yes |
| Complex joins | Limited | Better than saved search | Full SQL-style joins |
| Best for | Operational dashboards, workflow triggers | Finance analysis, trend exploration | Complex multi-table reporting |
When are saved searches the right reporting tool?
Saved searches are the default reporting tool for live NetSuite accounts. They are available on all editions, embed in dashboards, and connect to the workflow engine in ways that Workbook does not.
Operational dashboards and portlets
Saved searches can be embedded directly in NetSuite dashboard portlets, giving users a live view of open tasks, pending approvals, overdue items, and key metrics on their homepage. This embedding is not available with Workbook.
Workflow conditions and alerts
SuiteFlow workflows use saved searches as conditions: trigger a workflow when a saved search finds a matching record, or send an alert when a saved search returns results. Workbook and SuiteQL cannot be used as workflow conditions.
Formula columns and summary groupings
Saved searches support formula fields using NetSuite's formula syntax, allowing calculated columns, conditional logic, and summary groupings. For most operational reporting, this covers the full requirement without Workbook.
Scheduled alerts and reminders
NetSuite can send scheduled email digests based on saved search results. This is a native feature available on all editions: send a daily summary of open POs, overdue invoices, or pending approvals to a distribution list.
What saved searches cannot do
- Pivot table layout (row by column dimension analysis)
- Built-in charting beyond basic portlet charts
- Ad-hoc drag-and-drop field rearrangement
- Complex joins across more than two or three record types
When does SuiteAnalytics Workbook add value?
Workbook is best for finance team analysis and management reporting where pivot tables, charting, and exploratory views are needed. Verify your edition includes the SuiteAnalytics module before building Workbooks.
Pivot tables for finance analysis
SuiteAnalytics Workbook supports pivot tables for multi-dimensional analysis: revenue by month by category, expenses by department and period, or vendor spend by project. These layouts are not possible in saved searches.
Trend exploration and ad-hoc analysis
Workbook's interface is designed for exploratory analysis. Finance teams can drag fields, rearrange dimensions, and explore trends without rebuilding a saved search each time the question changes.
Built-in charting and visual outputs
Workbook includes chart types that saved searches cannot produce as standalone outputs: bar charts, line charts, and combination views that can be shared with management or exported alongside data tables.
When does a reporting requirement need SuiteQL?
SuiteQL is the reporting layer of last resort: for requirements that saved searches and Workbook cannot satisfy. It always requires developer time.
Complex multi-table joins
SuiteQL can join across record types that saved searches cannot directly connect, using SQL-style syntax. This is the only option for reports that require three or more record types joined with specific conditions.
Custom report pages (via Suitelet)
A Suitelet can execute a SuiteQL query and render the results as a custom page inside NetSuite with interactive filters, conditional formatting, and export options that saved searches and Workbook cannot provide.
Choosing the right tool for your NetSuite report
- Dashboard portlet for daily operations: Saved search. Embeds directly as a portlet; updates in real time as transactions post.
- Workflow condition or scheduled alert: Saved search. Workbook and SuiteQL cannot be used as workflow conditions.
- Finance team analysis with pivot tables: Workbook (if the SuiteAnalytics module is included in your edition).
- Complex join across three or more record types: SuiteQL, built by a developer into a Suitelet or Scheduled script.
- Export to Excel for management: Either saved search or Workbook; both export to CSV. Workbook exports are easier to format for presentation.
Related reading
- NetSuite saved searches and dashboards covers saved search builds for operational reporting and dashboard portlets.
- NetSuite SuiteScript development covers how SuiteQL is used in custom Suitelet report pages.
- NetSuite account optimization covers the broader scope of improving live NetSuite accounts including reporting.
Need custom reporting built in your NetSuite account?
Tell us what the report needs to show and we will assess whether saved searches, Workbook, or SuiteQL is the right tool.
Frequently Asked Questions
Does every NetSuite account include SuiteAnalytics Workbook?
No. SuiteAnalytics Workbook is part of the SuiteAnalytics module, which must be included in the NetSuite subscription. Saved searches are available on all editions without any additional module. Before building reports in Workbook, verify with your NetSuite account manager that the SuiteAnalytics module is included in your subscription.
Can a saved search be converted to a SuiteAnalytics Workbook?
Not directly. Saved searches and Workbooks are built in separate tools with different interfaces and data models. A saved search cannot be imported into Workbook, and a Workbook cannot be converted to a saved search. The two serve different use cases and are built separately.
Which is better for dashboard portlets: saved searches or Workbook?
Saved searches are better for dashboard portlets. NetSuite's native dashboard portlets use saved searches as their data source. Workbook outputs can be viewed in the Workbook interface but cannot be embedded as live portlets in a NetSuite dashboard the same way saved searches can.
Can SuiteQL be run without a developer?
SuiteQL must be run through a SuiteScript (a Scheduled script, Suitelet, or Restlet) because there is no UI in NetSuite for running SuiteQL queries directly. This means SuiteQL always requires developer involvement to build and deploy. Saved searches and Workbook can both be built entirely without code.
When should I use SuiteQL instead of a saved search?
Use SuiteQL when the report requires joins that saved searches cannot support, such as connecting three or more record types with complex conditions, or when the calculation logic is too complex for saved search formula syntax. For most operational reports and dashboards, saved searches are sufficient. SuiteQL is the right tool when a saved search reaches its structural limits.
Can saved searches handle formula calculations?
Yes. NetSuite saved searches support formula fields using NetSuite's formula syntax, which is based on Oracle SQL functions. You can write conditional expressions, math operations, date calculations, and string manipulations directly in saved search columns. For most financial and operational reporting, this covers the full requirement without needing SuiteQL or Workbook.
Ready to build the reporting your NetSuite account needs?
Describe the output you need. We will identify the right tool and give you a realistic build scope.