A NetSuite Saved Search is a stored query definition built through the NetSuite UI. Pick a record type, define criteria, choose result columns, optionally add summary functions. The result can be displayed in the UI, scheduled for email delivery as CSV, or exposed via REST API. Saved Searches are the most common reporting primitive in NetSuite but have limited JOIN support and no subqueries, making SuiteQL the better choice for complex external analytics.
What Saved Searches are good for
- Ad-hoc reports inside NetSuite — open up data, filter, summarize, share via permalink
- Scheduled email exports — set frequency (daily, weekly, monthly), email CSV to recipients
- Dashboard portlets — feed NetSuite home dashboards with KPI tiles
- Workflow triggers — Saved Searches can fire SuiteScript or Workflow actions based on result rows
- Simple list views — sales orders due this week, customers with overdue invoices, etc.
What Saved Searches can't do well
- Complex multi-table JOINs — limited to single primary record type with related-field traversal
- Subqueries / CTEs / window functions — not supported
- Parameterized queries — criteria are static at save time; cannot pass parameters at runtime
- Large data extracts — typically capped at 100,000 rows in UI; performance degrades with deep history
- Cross-subsidiary aggregation in OneWorld — currency translation + elimination requires post-processing
- Reliable schedule reliability — scheduled exports can silently fail; no native retry/alert
Saved Search vs SuiteQL
| Aspect | Saved Search | SuiteQL |
|---|---|---|
| Built via | NetSuite UI | SQL text |
| JOIN support | Limited (single primary record) | Full multi-table |
| Subqueries / CTEs | No | Yes |
| Window functions | No | Yes |
| Parameterization at runtime | No | Yes |
| Best for | In-NetSuite reports, dashboards, scheduled emails | External analytics, Power BI, Snowflake, complex JOINs |
Migrating Saved Searches to external analytics
Many teams accumulate hundreds of Saved Searches over years. When moving to Power BI, Snowflake, or another analytics destination, the temptation is to recreate each Saved Search as an external query. Better approach: extract the underlying NetSuite tables via SuiteQL into a star schema once, then build all your reports against that schema. Acterys NetSuite Sync ships pre-built star schemas + Power BI templates that replace 80% of typical Saved Search reports out of the box.
Related glossary entries
- SuiteQL — modern SQL-based alternative
- NetSuite REST Web Services — how SuiteQL is exposed
- SuiteAnalytics Connect — Saved Searches via ODBC