1. SuiteCloud Platform
  2. Customization
  3. Custom Forms
  4. Custom Sublists
  5. Example of Dynamically Filtering a Custom Sublist by a Record Field

Example of Dynamically Filtering a Custom Sublist by a Record Field

You can use NetSuite custom sublists and saved searches to automatically filter records displayed on a sublist for a record, based on a specific field value selected in the parent record. This capability enables users to see only the most relevant related records for the context of each parent record, which helps streamline content and simplify record review.

To use this feature, you should be familiar with creating custom lists, custom record types, and saved searches. For more information, see the following topics:

Scenario Example

Suppose your company tracks sales activity across different seasons. You have two custom record types: one for summary sales (Tracked Sales) and another for individual sales entries (Specific Sales). Each Tracked Sales record has a Season field designating the relevant season. Each Specific Sales record also includes its own Season field.

You want to provide users with a focused view of sales activity that matches the season selected on a particular Tracked Sales record. By configuring a custom sublist for Tracked Sales and linking it to a saved search filtered by season, you can display only those Specific Sales entries relevant to the selected season in the sublist. If you change the season on the parent record, the sublist updates automatically to display only the corresponding Specific Sales.

This setup creates a dynamic, data-driven relationship in your records. The value selected in the filter field of the parent record acts as a controller, and the related records shown in the sublist depend on this value.

General Steps to Set Up a Dynamically Filtered Custom Sublist

To implement this behavior, follow these high-level steps:

  1. Create custom record types as needed.

    For example, create a parent record type such as Tracked Sales and a related record type such as Specific Sales.

  2. Add a shared field to both record types.

    Include a field (such as Season) on both the parent and related record types. This field could be based on a custom list, custom record, or use an existing standard list/record field.

  3. Create a saved search on the related (child) record type.

    Set up a saved search for Specific Sales, making sure the shared field (such as Season) is added as the first available filter. This enables the saved search to filter results based on the corresponding value from the parent record.

  4. Add and configure the custom sublist on the parent record type.

    Attach a custom sublist to the parent record (such as Tracked Sales), select the saved search to provide the sublist data, and specify the relevant field (such as Season) for dynamic filtering. Selecting the correct field in the sublist definition ensures the displayed results match the current value on the parent record.

  5. Test and refine your setup.

    Review the behavior of the sublist as you change the filter field on the parent record and make adjustments as needed to ensure that only the relevant related records appear in the sublist.

Related Topics

General Notices