ANS-0037 · SAVED SEARCHES & FORMULAS
Why Do NetSuite Saved Searches Misbehave with Duplicate Class Names?
NetSuite's class matching logic, which relies on names rather than internal IDs, can lead to unexpected results when using the 'Classes (No Hierarchy)' option in transaction saved searches.
Short answer
NetSuite's class comparison logic in saved searches relies on the class name, not its internal ID. When multiple classes share the same name but differ only by their parent, using the 'Classes (No Hierarchy)' option can cause matching issues. This behavior is inherent to NetSuite's design and has been present for some time.
Scenario
Users may observe unexpected behavior in NetSuite transaction saved searches when filtering by classes, particularly when the 'Classes (No Hierarchy)' option is selected. This issue arises when multiple class records exist with identical names, differing only by their parent class. The system's matching mechanism struggles to differentiate these similarly named classes.
Solution
NetSuite's system for comparing and matching classes in saved searches relies on the class name rather than its internal ID. Consequently, when two or more classes share an identical name, their differentiation is solely based on their parent class. Selecting the 'Classes (No Hierarchy)' option in a transaction saved search bypasses this parent-based distinction, leading to problematic matching behavior. This design characteristic has been a long-standing aspect of NetSuite's functionality.
Expert NetSuite Support
Need help with this NetSuite issue?
Saved Searches & Formulas consulting and configuration support