Welcome back to another SuiteTip! In this article, we’ll look at a simple but highly effective way to improve Saved Search performance by optimizing your filters.
Saved Searches are powerful, but as your data grows, poorly defined criteria can slow them down significantly. While the existing documentation available explains how to define filters and criteria, it does not explicitly document indexing behavior. The tips below are based on common best practices used in real-world implementations.
To improve performance, focus on narrowing your dataset:
- Use commonly filtered standard fields, such as:
- Transaction Date
- Type
- Status
- Entity or Internal ID
- Apply filters in the Criteria tab rather than relying on the Available Filters in the Results page
- Avoid broad or expensive filters like:
- “Contains”
- “Is not empty”
- Open-ended date ranges
For Example:
Instead of:
Use:
- Date: within last 30 days
This reduces the volume of records evaluated and improves load time.
Notes:
- NetSuite does not publicly expose which fields are indexed
- Searches with multiple joins can still be slow even with good filters
- Formula-based criteria may impact performance if overused
Improving Saved Search performance often comes down to better filtering. By using targeted, commonly used fields and limiting your dataset early, you can significantly reduce load times and create a smoother user experience.
---
Stay tuned for our next SuiteTip, where we’ll explore more tips and best practices for navigating NetSuite Reports and Saved Searches!
We encourage you to share your own tips, ask questions, and engage with fellow community members. Your experiences can help others on their journey to becoming NetSuite analytics experts!