Fix NetSuite Saved Search vs Workbook Choice

Use a NetSuite Saved Search when the result must reach a role, dashboard, alert, or scheduled process. Use a SuiteAnalytics Workbook when the main job is exploratory analysis across related record families. Saved Searches provide repeatable operational outputs. Workbooks help you test a question before turning it into a report, chart, or search.

Start with the output you need

A Sales Manager needs the top 20 open sales orders by customer and sales representative, refreshed each morning.

A Saved Search fits this case. Go to Reports > New Search, select Transaction, and then select Sales Order. On Criteria, add Main Line is True and set Status to the open sales order statuses: Pending Approval, Pending Fulfillment, Partially Fulfilled, Pending Billing/Partially Fulfilled, and Pending Billing. Add Customer, Sales Rep, Document Number, and Amount on Results. Sort by amount so the largest orders come first, then save the search as Open Sales Orders by Rep.

NetSuite stores Main Line as a Boolean. True returns one row per transaction from the transaction body, while False returns line-level rows. With False, one order with five lines shows up five times, so an order-level list needs True. If the result must contain exactly 20 orders, trim it with a separate operational filter.

On the saved search, turn on Send Emails According to Schedule and set the morning cadence. To put the result on a dashboard, click Personalize, add the Custom Search portlet from the Standard Content tab, then click Set Up in the portlet and choose the search. The search now has an audience, refresh cadence, and fixed result set.

A workbook fits a changing question. The steps for building one are in the workbook section below.

Saved Search vs Workbook in NetSuite

The distinction is practical. A Saved Search answers, “What records do I need to act on?” A Workbook answers, “What pattern exists across these records?”

Use a Saved Search for operational delivery

Choose a Saved Search when the same result must appear in several places. Common examples include open opportunities by sales stage, invoices approaching their due date, low inventory items, and unapproved expenses.

For an invoice reminder, create a Transaction search with Type = Invoice, Main Line = True, and a due-date criterion based on the current date. Include Customer, Document Number, Due Date, and Amount Due. Use a Summary result for grouped counts or a KPI result when the audience needs a single metric.

Saved Searches support permissions and subscriptions. Restrict the audience through the search’s Audience setting, or publish it through a role-specific dashboard. Scheduled email, set up as in the sales order example above, covers the recurring delivery.

Use a Workbook for linked-record analysis

Workbooks are especially useful when a useful answer requires more than one record family. A sales analysis may need transactions, customers, locations, and items. A support analysis may need cases, contacts, and products.

Use a workbook when the question is still changing. Suppose finance wants to understand margin by customer, item, department, and location. Start with transaction data, add customer and item dimensions, then test several measures and filters. The workbook lets you compare alternatives before committing to a saved-search layout.

Here is the practical architecture:

1. Go to the Analytics Home page and, on the Workbooks subtab, click New Workbook.
2. Select a dataset built on transaction records.
3. Add related records such as Customers and Items to the dataset only when the analysis needs them.
4. Define measures such as Sum of Amount and Count of Documents, then filter by posted transactions, subsidiaries, or dates.
5. Build a pivot or chart using the dimensions under review.
6. Save the workbook with a name that describes its question and date range.

Oracle's Workbook Guide covers creating a workbook from an existing dataset.

Avoid adding every available relationship. Extra sources increase ambiguity and make the workbook slower to interpret. Add Items when item-level margin matters. Add Customers when customer attributes drive the comparison. Keep unrelated sources out.

Workbooks also handle charts well, but charting is not their only purpose. Their stronger use is testing relationships before converting a stable question into a saved search or dashboard component.

Convert a stable analysis into a search

Once the analysis stops changing, decide what should become permanent. If the result needs a fixed audience, scheduled delivery, or alert, recreate the stable dimensions and measures as a Saved Search. Keep the workbook as the discovery record.

Do not force every workbook into a search. A search that needs too many joins can become difficult to maintain. A workbook that produces the same executive chart every week may deserve a saved search or published report instead.

Permissions still matter after conversion. A workbook author may see fields that a dashboard viewer cannot access. Test the saved search under the intended role before publishing it. Also verify subsidiary restrictions, posting-period filters, and whether the result uses line-level or body-level transaction data.

Decision rule for daily use

If the answer drives an action, build a Saved Search. If the answer requires investigation, build a Workbook.

For a repeatable customer balance report, use a Saved Search. For comparing balances across customer class, location, and aging bucket, start with a Workbook. For a daily exception list sent to collections, return to a Saved Search with a schedule and audience.

The fastest workflow is often both: use a workbook to discover the useful dimensions, then publish the stable result as a saved search for the people who need it every day.