When a NetSuite Saved Search contains hundreds or thousands of records, users need more than static criteria. A NetSuite text box filter gives users a practical way to enter a value, phrase, number, or reference and narrow the displayed results without editing the search definition.
To set up a text box filter on a NetSuite Saved Search, open the search, go to the Available Filters subtab, add the text-compatible field, enable Show in Filter Region, select an appropriate operator such as contains or is, and save the search. When users open the search, NetSuite displays the available filter in the filter region, where they can enter a value and refresh the results.
The important distinction is that the filter must be added under Available Filters, not only under the search’s Criteria tab. Criteria determine which records the search returns by default. Available Filters control which fields users can adjust while viewing the results. We will walk through the setup, explain how text operators affect results, and cover the issues that cause a filter to behave differently than expected.
What Is a NetSuite Text Box Filter?
A NetSuite text box filter is an interactive field that allows a user to enter a value directly above a Saved Search result set. The user types a search term, applies or refreshes the filter, and sees records that match the selected field and operator.
For example, a customer Saved Search might display customers with columns for:
Customer name
Email address
Phone number
Sales representative
Customer status
External ID
Adding a text box filter for Name allows a user to search for a customer by entering part or all of the customer name. Adding a filter for Email gives users a different lookup method without changing the columns or permanent search criteria.
The exact behavior depends on the field type. A text field generally supports operators such as contains, starts with, is, and does not contain. A list or record field behaves differently because NetSuite may present a list selector or record lookup instead of a plain text entry box.
This distinction matters when you are designing a user-facing search. A filter that looks like a simple text search might actually be searching an internal ID, a display value, a joined field, or a formatted representation of the data.
How Do You Add a Text Box Filter to a NetSuite Saved Search?
The basic setup takes place on the Available Filters subtab of the Saved Search definition. The following process applies to most standard Saved Search record types, although the available fields and operators vary by record type, permissions, and account configuration.
Open the Saved Search you want to modify.
Select the Available Filters subtab.
In the filter field row, choose the field users should search. Common choices include Name, Document Number, Email, Memo, External ID, or a custom text field.
Enable Show in Filter Region for that field.
Select the appropriate filter operator if NetSuite exposes an operator choice for the field.
Add a clear filter description if the displayed field name is not obvious to end users.
Save the Saved Search and test the filter from the search results page.
The most important step is selecting the right field. If users need to locate a sales order by its visible transaction number, choose the field that represents the transaction number rather than an internal identifier. If they need to search notes, choose a memo or custom text field, but confirm that the field is included in the search’s record context.
For the broader role of Saved Searches in operational reporting, see our overview of NetSuite reporting tools and record-level reporting. This article focuses specifically on interactive text filtering rather than the full reporting landscape.
Which Fields Work Best With a Text Box Filter?
Text box filters work best with fields whose values are predictable, searchable, and meaningful to the person using the Saved Search. The best field is not always the field that stores the most data. It is the field that lets users identify the right record with the least ambiguity.
Useful candidates include:
Name fields: Customer, vendor, employee, contact, and item names are common choices for interactive lookup.
Transaction numbers: Document numbers help users find sales orders, invoices, purchase orders, and other transactions when the number is known.
External IDs: External IDs are useful when another system, spreadsheet, or integration provides the reference value.
Email fields: Email filters support customer, contact, and employee searches when addresses are consistently maintained.
Memo and custom text fields: These fields are helpful for reference notes, legacy identifiers, project codes, or process-specific tags.
A field containing inconsistent free-form data requires more careful design. For example, a memo field might contain several abbreviations for the same concept. A contains operator will return technically matching records, but the result set may still be incomplete if users enter a phrase that does not match the stored wording.
NetSuite custom fields also have separate search and visibility considerations. A custom field being searchable in Global Search does not automatically mean it is the best field for every Saved Search filter. For context on that distinction, see our guide to making NetSuite custom field values searchable.
How Do NetSuite Text Filter Operators Change the Results?
The operator determines how NetSuite compares the user’s entry with the stored value. Choosing the wrong operator is one of the fastest ways to make a text box filter appear broken.
Contains
Contains returns records where the entered text appears anywhere in the field. If the stored value is “Northwind Distribution” and the user enters “wind,” the record matches.
This is the most flexible operator for general lookup, especially when users know only part of a customer name, memo, or external reference. Its tradeoff is a broader result set, particularly when the field contains common words or short character strings.
Is
Is requires an exact match based on NetSuite’s field comparison behavior. It is appropriate for a precise document number, external ID, or controlled code.
Exact matching is useful when users know the complete value. It is less forgiving when users enter a partial name, add an extra space, or use a different format from the stored record.
Starts With
Starts With returns records where the field begins with the entered value. It works well for naming conventions such as customer codes, item prefixes, or document references that follow a consistent pattern.
It is more controlled than contains, but it fails when the useful search term appears in the middle or at the end of the value.
Does Not Contain
Does Not Contain excludes records that include the entered text. This is useful for temporary investigation, but it is rarely the best default for an everyday lookup filter because users may not understand why records disappear.
The available operators depend on the field type and NetSuite’s handling of that field. A list field, date field, checkbox, or numeric field will expose different comparison options. Do not assume that every field supports the same text behavior.
How Should You Configure the Filter Region for End Users?
A text box filter is only useful when users understand what to enter and what the results represent. Filter design is therefore a usability task as much as a configuration task.
Start with the label users recognize. A field called Internal ID might be technically accurate but confusing if users think in terms of customer numbers or transaction numbers. Use the filter description to provide context when the default label is ambiguous.
For example, a description such as Enter part of the customer name gives clearer guidance than simply displaying Name. For a custom reference, a description such as Search by legacy customer code explains both the expected value and its business purpose.
Avoid exposing every searchable field. Too many available filters make the filter region harder to scan and increase the chance that users select the wrong field. A focused filter region typically includes the two or three lookup fields people use most frequently.
The filter region also needs to work with the search’s audience. A finance user may prefer document number and account. A service user may need customer name, case number, and email. The same Saved Search should not automatically expose every field simply because NetSuite makes it available.
If the search is used as a dashboard reminder, scheduled email, or operational queue, keep interactive filters aligned with the action users take after finding a record. A text filter that returns records but does not help users prioritize or open the correct record adds friction rather than removing it.
Why Is My NetSuite Text Box Filter Not Working?
A text box filter that returns no results or too many results usually has a field, operator, data, or context problem. Check the filter definition before changing the search’s permanent criteria.
The first issue is often the wrong field. NetSuite may display a value through a joined field while storing the searchable value elsewhere. For example, a transaction search may show a customer name through a join, but the user may actually need to filter the transaction’s entity field.
The second issue is the operator. A user searching for “Acme” expects a partial match, but an is operator may require the complete stored value. Change the operator to contains when partial lookup is the intended behavior.
The third issue is formatting. Document numbers, phone numbers, email addresses, and external IDs might contain punctuation, prefixes, spaces, or leading zeros. Test the filter with a value copied directly from a result row before concluding that the filter is invalid.
The fourth issue is search criteria. An Available Filter cannot return a record excluded by the search’s existing criteria. If the Saved Search only includes active customers, a text filter cannot reveal an inactive customer, even when the name matches.
The fifth issue is permissions and role context. A result visible to an administrator may not be visible to another role because of subsidiary restrictions, employee permissions, record restrictions, or field-level access. Test the search using the role that will actually use it.
Finally, verify whether the filter is visible in the filter region. Adding a field to Available Filters without enabling Show in Filter Region does not give users an interactive entry field on the results page.
How Can You Test a Saved Search Text Filter Properly?
Test the filter with known records rather than random values. Choose one record that should match, one record that should not match, and one record that tests partial matching.
A practical validation sequence is:
Enter a complete value and confirm whether an exact match appears.
Enter a distinctive partial value and confirm the behavior of contains or starts with.
Test capitalization and punctuation where relevant.
Clear the filter and confirm that the original result set returns.
Test the search under the intended role.
Check the search with records from each relevant subsidiary, status, or permission scope.
Pay attention to whether the filter refreshes automatically or requires the user to submit or refresh the search. NetSuite interface behavior can vary by page context and account configuration, so document the expected interaction for the people who use the search.
Also test the filter alongside other available filters. A name filter combined with a status filter should narrow the result set in a predictable way. If users apply several filters, confirm whether the combination reflects an AND relationship and whether the resulting set still supports the intended workflow.
Do not test only from the Saved Search editor. The editor confirms that the field exists, but the results page confirms whether the filter is understandable, visible, responsive, and useful to the final audience.
Text Box Filters vs. Permanent Criteria: Which Should You Use?
Use permanent criteria when every user should see the same baseline population. Use an Available Filter when users need to refine that population differently during each search session.
For example, a Saved Search for open sales orders might use permanent criteria for:
Main line equals true
Status equals Pending Fulfillment
Closed equals false
An Available Filter for customer name or sales representative then lets users narrow the operational queue without changing those baseline rules.
This structure protects the search from accidental overreach. Users can search within the approved population, while administrators retain control over the records included by default.
A permanent criterion is better for compliance, workflow boundaries, and business definitions. An Available Filter is better for ad hoc lookup, queue ownership, and user-driven investigation. Combining both produces a search that is consistent enough for reporting and flexible enough for daily work.
When Should You Use a Different NetSuite Search Approach?
A text box filter is not the right solution for every search requirement. If users need complex Boolean logic, multiple alternate criteria, or calculations across large volumes of data, the Saved Search might need a different design.
Consider a different approach when:
Users need to search across unrelated record types that are not available through joins.
The search requires fuzzy matching, normalization, or advanced text processing.
The result set is too large for a practical interactive lookup.
Users need aggregated trends rather than individual records.
The filter value must come from a workflow, script, or external application.
The search requires a custom interface with guided inputs and validation.
A Suitelet or SuiteScript solution becomes more appropriate when the interface needs custom controls, multi-step logic, or processing that standard Saved Search filters cannot provide. For a single record type with straightforward criteria, however, Saved Search remains easier to maintain and faster to adjust.
We help teams evaluate these boundaries through NetSuite consulting and customization support. The right answer is not always more code. A carefully designed Available Filter often solves the immediate lookup problem without introducing a custom maintenance burden.
Conclusion
A NetSuite text box filter gives users a simple way to search Saved Search results without editing the underlying search. The configuration is straightforward, but the quality of the result depends on choosing the correct field, selecting an operator that matches user expectations, exposing the filter clearly, and testing it under the intended role.
Use contains for flexible partial lookup, is for exact controlled values, and starts with for predictable prefixes. Keep permanent criteria responsible for the search’s baseline rules, then use Available Filters for user-driven refinement. When standard Saved Search behavior no longer supports the required logic or interface, evaluate SuiteScript or a custom NetSuite solution instead of forcing the filter to do work it was not designed to handle.
