1. SuiteCloud Platform
  2. Customization
  3. Custom Segments
  4. Custom Segment Creation
  5. Filtering for a Custom Segment
  6. Filtering Custom Segment Values on Custom Records Example

Filtering Custom Segment Values on Custom Records Example

You can apply segments to both standard and custom record types—even when filtering by standard segments (Class, Department, Location, Subsidiary) is enabled. However, it’s important to understand how filtering behaves differently on custom records compared to standard records.

This topic illustrates a real-world example of custom segments for U.S. State and U.S. City and discusses how filtering behaves under different conditions.

Filtering U.S. City by U.S. State and Subsidiary

Suppose your company operates in multiple subsidiaries and you want to track city and state information for both standard transactions and a custom record type called Contract.

You create two custom segments:

On Standard Records

On a standard record, such as a transaction, when you select a value for Subsidiary and U.S. State, the available values in the U.S. City segment are filtered based on both selections. For example, if Subsidiary = US Subsidiary and U.S. State = California, only cities in California for the US Subsidiary (for example, Los Angeles, San Francisco) are available.

Here’s how the custom segment filtering setup for this scenario looks:

Custom segment Filter by field showing filtering setup example.

On Custom Record

The Contract custom record doesn’t have a Subsidiary field. When you select a value for U.S. State, the available values in the U.S. City segment are filteredcreating a only by U.S. State. Filtering by Subsidiary is ignored because the Subsidiary field doesn’t exist on the custom record.

For example, if U.S. State = California, all cities in California are available, regardless of subsidiary, as shown in this image:

Custom segment Filter on a Contract record showing filtering of US city based on US state.

Filtering by class, department, location, and subsidiary applies only to records that contain these fields. For custom records that don't have these fields, this type of filtering isn't applicable and is ignored.

Example Walkthrough

How this works in practice:

  1. You create a custom segment U.S. City filtered by U.S. State and Subsidiary.

  2. You apply both segments to the Contract custom record.

  3. On a Contract record:

    • You select California in the U.S. State segment.

    • The U.S. City segment displays Los Angeles and San Francisco—both cities in California.

    • Because the Contract record doesn't have a Subsidiary field, subsidiary filtering isn't applied.

Consequently, you can still choose the correct city for the selected state, but the subsidiary filter isn't considered.

Benefits of Filtering Custom Segment Values on Custom Records

Previously, if you wanted to use filtering by Subsidiary but also needed to apply the segment to custom records, you faced difficult workarounds—such as duplicating segments or building complex validations. Now, you can use the same segment across standard and custom records, and NetSuite automatically applies only the filters that are relevant to each record type.

Notes:

  • The Filter by field on the segment setup page displays the intended filtering, but on custom records, only filters for fields that are present on the record are applied.

  • When a segment is filtered by another custom segment, NetSuite automatically ensures both segments are applied to the record.

Related Topics

General Notices