ANS-0011 · SAVED SEARCHES & FORMULAS
How to Resolve Inaccurate NetSuite Summary Item Search Results
When NetSuite search criteria involving joined member items and transactions produce incorrect summary results, a PL/SQL statement can provide an accurate solution.
Short answer
Inaccurate NetSuite summary item search results, particularly when criteria use negation or involve joined member items, can be resolved by replacing standard UI criteria with a PL/SQL statement. Implement a CASE WHEN {memberitem.name} LIKE ('%TPM%') THEN 0 ELSE 1 END | equal to 1 condition to ensure precise data retrieval.
Scenario
NetSuite's user interface functionality for constructing search criteria can sometimes yield inaccurate results. This issue is frequently observed in searches where the criteria utilize a negation, such as "does not contain," especially when dealing with summary item searches joined to member items and transactions.
Solution
To correct inaccurate summary item search results, particularly when standard UI criteria with negation produce errors, implement a PL/SQL statement directly within the search criteria. For example, to filter based on a member item name, use the following PL/SQL condition:CASE WHEN {memberitem.name} LIKE ('%TPM%') THEN 0 ELSE 1 END | equal to 1This approach ensures accurate data retrieval by bypassing potential UI interpretation issues with complex or negated criteria.
Expert NetSuite Support
Need help with this NetSuite issue?
Saved Searches & Formulas consulting and configuration support