The NetSuite Saved Search Guide

Criteria are the rules that decide which records a saved search returns, and getting them right is most of the skill. You can filter on standard fields, custom fields, and related-record fields, and combine them with AND and OR logic to express precise questions. For example, transactions where type is Invoice, status is Open, and due date is before today returns exactly your overdue invoices.

Two features add real power. Available filters let users refine results interactively when they run the search, without editing it. Formula criteria let you filter on calculated expressions when a standard field will not do. The discipline is to start broad, confirm the record set looks right, then tighten the criteria, rather than writing complex logic blind and wondering why nothing returns.

The Results tab controls what the search shows and how. You choose the columns, set their order, and define sorting. The real leverage comes from summary types: applying Sum, Count, Average, Minimum, or Maximum, combined with grouping, transforms a long list into a summarized view, such as total sales grouped by month or item count grouped by location.

Summary searches are what make saved searches feel like analytics rather than just filtered lists. A single search can show revenue by sales rep, aged receivables by customer, or inventory value by category. Add a chart to the results and the same search becomes a visual you can drop straight onto a dashboard, which is where saved searches turn into the KPIs leadership watches every day.

Formulas unlock the advanced tier of saved searches. NetSuite supports SQL-style formula fields in both criteria and results, so you can calculate values that do not exist as standard fields. Common uses include combining fields, calculating the number of days between dates, categorizing records with CASE logic, and formatting text or numbers for cleaner output.

For example, a formula can compute days overdue as the difference between today and an invoice due date, or a CASE expression can bucket customers into tiers by revenue. Formulas do require learning a bit of SQL function syntax, which is where many users hit their ceiling and where expert help pays off. Used well, formula fields let a single saved search answer questions that would otherwise need a report writer or an export to a spreadsheet.

A saved search becomes far more valuable when it lives on a dashboard. NetSuite lets you surface saved searches as list portlets, KPI portlets, and KPI scorecards, and as report snapshots and charts, so the numbers you care about are the first thing you see when you log in, always current.

Because dashboards are role-based, you can give each team the live metrics that matter to them: cash and receivables for finance, pipeline for sales, stock exposure for operations. Saved searches can also drive reminders and email alerts, so a threshold breach reaches the right person without anyone running a report. This is how a well-built library of saved searches quietly becomes the reporting backbone of the whole business.

A tidy saved search library is an asset; a messy one is noise. Name searches clearly and consistently so people can find them, and use a naming convention such as a team or purpose prefix. Set access deliberately so sensitive data is not exposed and dashboards are not cluttered. Reuse rather than duplicate: build criteria once and refine, instead of creating near-identical copies.

Beyond hygiene, favor summary searches over huge raw lists for performance, add available filters so one search serves many needs, and review the library periodically to retire searches no one uses. Test a search after you build it to confirm it returns exactly what you expect. These habits keep saved searches fast, trustworthy, and genuinely useful rather than a sprawl of forgotten queries.