Defining Standard Search Filters
On the Criteria, Standard subtab of an advanced or saved search, you can set up filters using fields from the record type, join fields from related records, and formulas. For some searches, you can also use values from attached files as filters.
To use a saved search as a custom KPI for multiple date ranges, don't add a date field as a filter on the Criteria subtab. For more information, see Notes on Using Saved Searches as Custom KPIs.
To define a field value from the selected record type as a filter:
-
Select the field from the Filter dropdown list. The fields are listed in alphabetical order.
-
Click the Set Description button
next to the filter field to open a popup window where you can enter a value and search logic (if available). -
Click Add to choose the next filter.
To define a join field value from a related record type as a filter:
-
Select the related record type in the Filter dropdown list.
Note:Related record types that have join fields you can use as filters are listed at the end and have ‘...’ after their name, for example, Account Fields....
-
In the first popup window that appears, select the join field from the related record type you chose.
-
In the next popup window, enter a value and search logic (if available) for the filter field, then click Set.
-
Click Add to choose the next filter.
For a list of related record types with join fields available for each search, see Related Records Fields Available for Advanced Searches.
To define a formula as a filter:
-
Select a Formula option from the Filter dropdown list.
-
Click the Set Description button
to open a popup window where you can enter the formula. -
Click Add to choose the next filter.
For more information, see Formulas in Searches.
To use parenthetical expressions to define search filters, check the Use Expressions box. For more information, see Using Expressions in Search Criteria.
To define a field from an attached file (such as the file's name) as a filter:
-
Select File Fields... in the Filter list.
-
In the popup window, select a field from the File Filter list.
-
Click the Set Description button
, enter or select a value for the filter field, and click Set. -
Click Add to choose the next filter.
For more information, see Searching by File Attachments.
Using Encrypted Fields in Searches
Searches and saved searches let you use custom fields with encrypted values. You can use encrypted fields in search results columns and in search filters, but only with a few operators (is, is not, is empty, is not empty). However, you can't use encrypted fields in search formulas, highlighting, summary results, or summary criteria.
SuiteScript doesn't support saved searches with encrypted values. Credit card numbers show up in search results only if you have the View Unencrypted Credit Card Numbers permission.
Defining Preferred Vendor Filter for Item Search in OneWorld Account with Multiple Vendors Feature Enabled
If you use the Preferred Vendor field as a filter in an item search in a OneWorld account with the Multiple Vendors feature enabled, you may run into this issue: If an item has more than one preferred vendor, the search only shows the item under the first preferred vendor listed. This happens because you can have different preferred vendors for each subsidiary in a OneWorld account with the Multiple Vendors feature enabled.
To avoid this, use both the Vendor field and Vendor is Preferred field as filters in your item search, instead of only Preferred Vendor. Set the Vendor filter to any vendors you want, and set Vendor is Preferred to Yes. This way, the item search will return all items where at least one subsidiary has any of your chosen vendors as the preferred vendor.
Limitations on Credit Card Number Search Filters
To keep customer credit card information secure, you can use only is empty or is not empty as operators for the Credit Card Number field in search filters. This applies to searches in the NetSuite UI and to searches run through SOAP web services, SuiteScript, and SuiteFlow.
The Credit Card Number search criteria field is a box type field. On the Criteria subtab, you can filter by Yes or No to show if a record has a credit card number, but you can't search for specific credit card numbers.
To follow these rules, saved searches that used operators such as contains, is, or is not with the Credit Card Number field have been deleted from all NetSuite accounts.
Limitations on Transaction Search Filters
Opportunity fields in a transaction search show data only for opportunities linked to other transactions that match your search criteria. To see all opportunity data, use an Opportunity search instead.
If you add the Created From field to your transaction search results, line-level fields don't show values. That's because the join to the source transaction's Created From field is at the main body level, not the line level.
Sometimes, you can use Applied To Transaction fields to get values for line-level fields. For example, if an invoice's source transaction is a sales order, the join is at the line level, so you get line-level values. However, if the source is an estimate, the join is at the main body level, so you don't get line-level values. For more information, see Saved Searches.
Limitations on Long Text and Rich Text Search Filters
If you use contains filters on Long Text and Rich Text text fields, the matching string is limited to approximately 500 characters. This limit can change depending on the character encoding.
Defining On Hand and Location On Hand Filters for Item Searches
There's a difference between the On Hand and Location On Hand fields that you can use in searches. On Hand shows the total quantity across all locations, while Location On Hand shows the quantity at each specific location.
This difference also applies to these pairs of fields:
-
Available and Location Available
-
Average Cost and Location Average Cost
-
Back Ordered and Location Back Ordered
-
Committed and Location Committed
-
On Order and Location On Order
-
Preferred Stock Level and Location Preferred Stock Level
-
Reorder Point and Location Reorder Point
-
Total Value and Location Total Value
For more information, see Saved Searches.