ANS-0185 · SAVED SEARCHES & FORMULAS

NetSuite: Using Private Saved Searches in Custom Dropdown Fields

While standard NetSuite configurations require public saved searches for sourcing, custom SuiteScript can provide a workaround for private searches.

Short answer

Standard NetSuite sourced list/record fields only display public saved searches. To use private saved searches, a custom SuiteScript solution is required. This involves performing a 'search of searches' to retrieve private saved searches and then programmatically populating a custom dropdown field using SuiteScript 2.x's N/ui/serverWidget module.

Scenario

A user needs to populate a list/record field with options derived from a NetSuite saved search. The challenge arises when the desired saved search is not public, and the standard field configuration only allows public saved searches to be sourced. This limitation prevents the use of private or restricted saved searches in standard dropdowns.

Solution

When configuring a standard sourced list/record field in NetSuite, it is a requirement that the saved search used for sourcing be set to Public. This ensures that the search results are accessible for display in the field. For scenarios requiring the use of private saved searches, a custom SuiteScript solution can be implemented. This approach leverages the capability to perform a 'search of searches' to programmatically retrieve saved search definitions, including private ones. Once the desired saved searches are identified, their results can then be used to populate a custom dropdown field. In SuiteScript 2.x, the programmatic population of dropdowns is achieved using the N/ui/serverWidget module, which provides the necessary functions to create and manage UI elements dynamically.

Expert NetSuite Support

Need help with this NetSuite issue?

Saved Searches & Formulas consulting and configuration support

Talk to a consultant