A NetSuite saved search is a reusable query that pulls records based on criteria you define and displays them in a custom result layout. You choose the record type, apply filters, select result columns, and optionally add sorting, grouping, summary logic, formulas, scheduled email delivery, or dashboard visibility.
Unlike many standard reports, saved searches are highly flexible. They are commonly used for operational reporting because they return live data and can be adapted quickly to changing business needs.
Typical use cases include:
Saved searches can also be shared, scheduled, pinned to dashboards, or used alongside NetSuite workflows to support process automation.
Use a saved search when you need flexible, real-time data with custom criteria. Use a standard report when presentation and formatting matter more than configuration flexibility.
| Feature | Saved Search | Standard Report |
|---|---|---|
| Real-time data | Yes | Yes |
| Custom formula fields | Yes | Limited |
| Schedule for email delivery | Yes | Yes |
| Trigger workflow automation | Yes | No |
| Access custom record types | Yes | No |
| Native charts/visualizations | No | Yes |
| Executive-ready formatting | No | Yes |
| Dashboard portlet integration | Yes | Limited |
A practical way to choose:
Before creating or editing a saved search, confirm your role has the right permissions.
Admins can review these permissions under Setup > Users/Roles > Manage Roles. Sharing issues often come from role restrictions or Audience settings rather than the saved search itself.
Go to Reports > Saved Searches > All Saved Searches, then click New.
In some accounts, the path may be Lists > Searches > Saved Searches > New.
If you do not see either option, your role may be missing saved search permissions. In that case, contact your administrator or a NetSuite consulting partner.
NetSuite will ask which record type you want to search. This choice determines the core dataset the search can access.
Common record types include:
Choose the record type that contains the main records you want to analyze. You can pull related fields later through joins, but the base record type shapes the search.
The Criteria tab determines which records are included.
Each filter has three parts:
For example, a customer inactivity search might use:
A transaction-based overdue invoice search might use:
Use multiple filters together to narrow the result set to the records that matter.
The Results tab controls what appears in the output.
Here you can:
For example, you might show:
If you are creating a summary search, make sure summary types are configured consistently. Mixed summary and non-summary columns can cause errors if not set correctly.
Formula fields let you calculate, classify, or reformat data directly in the search.
Available types typically include:
Choose the formula type that matches the kind of value you want to return.
Examples:
Date formula {trandate} + 90
Use this in a Formula (Date) field to calculate a date 90 days after the transaction date.
Text formula {companyname} || ' - ' || {accountnumber}
Use this in a Formula (Text) field to combine multiple text values.
Overdue status formula CASE WHEN {daysoverdue} > 0 THEN 'Overdue' ELSE 'Current' END
This is useful in a Formula (Text) result column to classify records clearly.
Margin percentage formula ({amount} - {estgrossprofit}) / {amount} * 100
Use a numeric or percent formula to show transaction margin.
Formula fields are often the difference between a basic data pull and a business-ready report.
If you are also exploring newer NetSuite AI capabilities, formula strategy becomes even more important as reporting features continue to evolve.
Before saving, preview the search and make sure:
Then:
A clear title helps other users understand the purpose immediately, such as:
Once the search works, customization makes it more useful for the team that will rely on it.
Formula fields can help turn raw data into action-ready information.
Examples include:
Instead of forcing users to interpret raw columns manually, formulas let the search explain the result.
You can include fields from related records by selecting joined fields in the Results tab.
Examples from a Transaction search might include:
This is useful when the base record type does not contain all the context you need.
As a rule, joins are fine for simple related fields. If your search becomes too dependent on multiple layered joins, performance may suffer. That is often the point where SuiteAnalytics Workbooks become the better reporting option.
Sorting helps users prioritize records quickly. For example:
Grouping and summarizing are useful for management-level reporting. You might:
Be explicit with summary settings to avoid result configuration errors.
The Audience tab determines who can access the saved search.
You can share by:
Use this carefully. Searches that expose margin data, compensation-related records, or vendor pricing should be restricted to the right audience. Public searches should be reviewed regularly.
Scheduling turns a saved search into an automated report.
After saving the search, open it again and go to the Email tab. Then enable Send Emails According to Schedule.
You can typically send results to:
Then choose a cadence such as:
Common patterns:
Depending on the audience, you may choose:
Choose the format based on how the recipients actually use the report.
This setting is critical.
If Summarize Scheduled Emails is unchecked, NetSuite may send one email per returned record instead of one consolidated email. That can create a flood of messages for every recipient.
For most reporting use cases, this box should be checked.
If you need help cleaning up a misconfigured scheduled search, a NetSuite support services team can usually help resolve the issue quickly.
If needed, you can also save each scheduled run to the NetSuite File Cabinet. This is useful for:
To show a saved search on a NetSuite dashboard:
Dashboard portlets are especially useful for live operational monitoring. Teams can use them to track:
Because the data is live, users get instant visibility without running the full search manually.
Below are practical saved search examples by function.
1. Overdue Invoice Search Transaction search filtered to open invoices with days overdue greater than zero. Best for a daily AR review.
2. Vendor Bills Due in 7 Days Transaction search filtered to open vendor bills due within the next seven days. Useful for AP planning.
3. Customer No-Activity Report Customer search filtered to active customers with no recent transaction activity. Often used by sales or account management teams.
4. Inventory Below Reorder Point Item search comparing quantity on hand to preferred stock level, often grouped by location.
5. Open Purchase Orders Past Expected Receipt Date Transaction search filtered to purchase orders pending receipt where the expected receipt date has passed.
6. Items With No Sales in 180 Days Inventory or transaction-based search to identify slow-moving or dead stock.
7. Expense Reports Awaiting Approval Search filtered to expense reports still pending supervisor or manager approval.
8. Open Sales Opportunities by Close Date Opportunity search showing active deals ordered by expected close date.
9. Project Budget vs. Actual by Project Manager Project search summarized by manager with budget and actuals shown side by side.
This is one of the most damaging avoidable mistakes. Always verify the summarize setting before turning on delivery.
Name and description fields are often slower than IDs, numbers, and standard date fields. Lead with indexed fields when possible.
If the output is a date, use Formula (Date). If it is text, use Formula (Text). Type mismatches can cause vague errors.
Too many joins increase complexity and execution time, especially on dashboard searches or frequently run reports.
Public saved searches should be reviewed for exposed financial or personnel data. Use the Audience tab carefully.
Saved searches can affect the user experience if they are poorly designed, especially when they run on dashboards or are shared broadly.
Use these best practices:
If a search is slow, simplify the criteria, reduce joins, tighten the date range, and confirm it is not doing unnecessary work. For broader tuning strategies, review these NetSuite optimization best practices.
Saved searches are excellent for operational reporting, but they are not always the right long-term solution.
Consider SuiteAnalytics Workbooks when you need:
Saved searches are best when you need quick, focused, real-time operational output. Workbooks are better when the question is broader, more analytical, or more visual.
You may also want to review NetSuite’s SuiteQL documentation if your team is moving beyond standard saved search capabilities. If you need help deciding which reporting layer fits your use case, working with a NetSuite consultant can speed up that decision.
If you need implementation, optimization, or troubleshooting support for your NetSuite environment, there are several helpful resources available that can guide you through best practices and expert solutions. You can start by exploring the NetSuite platform overview to understand the full capabilities of the system and how it supports business operations. For more hands-on expertise, consider leveraging NetSuite consulting services or ongoing assistance through NetSuite support services. To enhance system performance and efficiency, review ERP optimization best practices, which provide actionable strategies for improvement.
If you're looking for specialized expertise, the NetSuite consultant resources page offers valuable insights, while a broader range of solutions can be found under NetSuite services. For quick productivity gains, check out the NetSuite Keyboard Shortcuts reference. You can also stay ahead with innovation by exploring NetSuite AI and Generative AI capabilities.
If you need immediate help, you can always Book a 30-Minute Fix Session for targeted support.
NetSuite saved searches are one of the fastest ways to improve visibility and reduce manual reporting inside NetSuite. Once your team knows how to build them correctly, they can support recurring operational reporting, automate scheduled delivery, and surface live exception data where people actually work.
Start with one high-value use case, such as:
Build the search, test the filters, verify the output, then schedule or publish it only after reviewing the audience and email settings carefully.
If you need help building or refining more advanced reporting, NetSuite services can help support more complex saved search and analytics work.
A NetSuite saved search is a reusable query that pulls records based on criteria you define, displays them in a customizable format, and can be shared, scheduled, or used for automation.
Go to Reports > Saved Searches > All Saved Searches > New, choose a record type, add Criteria filters, define the Results columns, then save the search.
Open the saved search, go to the Email tab, enable scheduled delivery, set recipients and frequency, choose the output format, and check Summarize Scheduled Emails.
Saved searches are more flexible for operational reporting and formulas. Reports are better for formatted presentation output.
Common causes include non-indexed filters, too many joins, complex criteria formulas, wildcard searches, and oversized result sets.
Yes. NetSuite workflows can use saved searches to target records for automated actions.
Use Workbooks when you need more complex joins, larger datasets, visualizations, or broader analytical reporting.
Disclaimer: This content is for general informational purposes only and may not reflect current updates or your specific configuration—please confirm details with your Anchor Group consultant.
Tagged with Training