Limitations on Search Filters
Keep these limitations in mind when setting up advanced and saved search filters:
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.