A saved search is NetSuite's built-in tool for finding, filtering, and reusing a specific set of records, customers who haven't ordered in 90 days, invoices still unpaid past terms, inventory below a reorder point, without writing any code. It's the first thing most NetSuite admins reach for, and for a lot of day-to-day reporting it's genuinely enough. We get called in once a saved search needs to feed another system automatically or run a calculation its criteria builder can't express.
A saved search is built from criteria (which records to include) and results (which fields to show), and NetSuite lets you reuse that combination as a list, a report, a dashboard portlet, or a scheduled email that lands in someone's inbox on a recurring basis. Built right, it replaces a lot of what used to be a manual filter-and-export routine.
They can trigger action too. A saved search set up as an alert can notify someone the moment a record matches its criteria, a customer's balance crosses a threshold, a case sits open past a certain number of days, without anyone running the search by hand to check.
For straightforward reporting, counting open orders by region, listing overdue invoices, pulling a customer list by segment, a saved search usually covers it with no custom development at all.
Saved searches have real limits: a cap on how many formula fields you can add, no support for complex multi-level joins across unrelated record types, and performance that degrades on very large result sets. Searches for "netsuite saved search sql" show up because the criteria builder's own formula language only goes so far before someone wants to just write the query directly.
The other common wall is getting data out automatically. A saved search can email a CSV on a schedule, but turning that into a live feed into another system, a BI tool, a partner portal, a reporting dashboard that isn't NetSuite, means someone opening that email and importing the file by hand, or it means pulling the same data through NetSuite's API instead.
Instead of a scheduled CSV email someone has to open and import, we pull a saved search's results through NetSuite's API on a schedule and land them directly in the system that needs them, a BI tool, a spreadsheet, a partner-facing dashboard.
When a report needs a calculation, a join, or a lookup beyond what the criteria builder supports, we build it as a scripted search or a SuiteAnalytics workbook instead, so the business gets the answer without fighting a tool that wasn't built for it.
Tell us what you do with the CSV once it lands in your inbox, and we'll scope how much of that step can disappear entirely.
A saved search is a great starting point, not a ceiling. If you're hitting its formula limits, exporting its results by hand, or wishing it fed another system automatically, describe the gap and we'll scope the fix, a scheduled pull, an API feed, or something else entirely. NetSuite is just one of the platforms we build this kind of thing on top of.
Let's talk →It's NetSuite's built-in way to filter and reuse a specific set of records based on criteria you define, then show the results as a list, a report, a dashboard portlet, or a scheduled email. It's one of the most-used features in NetSuite precisely because it covers routine reporting without writing any code.
Yes, directly to CSV or Excel from the results screen, or on a recurring schedule if you set the saved search up to email itself. For a one-off look at the data that's usually enough. For getting the same data into another system automatically and repeatedly, most businesses eventually want something pulling it through the API instead of someone opening an email and importing a file each time.
Yes, you can run a saved search's logic and pull its results through SuiteScript or NetSuite's web services API rather than only through the UI. That's the layer that lets a saved search's results flow into another system on a schedule instead of staying a manual export.
A saved search is quicker to build and fine for most filtering and list-based reporting. A SuiteAnalytics workbook, NetSuite's more modern reporting tool, handles pivoting, visual charts, and more complex data relationships that a saved search's criteria builder isn't designed for. We cover that side of NetSuite in more depth here →
Building the search itself usually doesn't need a developer. Where businesses get stuck is everything around it: formulas the criteria builder can't express, getting results into a system outside NetSuite automatically, or performance problems once a search runs against a few hundred thousand records. That's where the work shifts from configuration to actual development.