---
sourceDocument: Brazil Sales Customer Relationship Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/order-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Sales Customer Relationship Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# Creating an associated picklist set

# Creating an associated picklist set {#ariaid-title1}

Release version: Brazil  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Creating an associated picklist set

ServiceNow CPQ allows you to create an associated picklist set as an alternative to a regular set field when defining new sets.
This feature links a multi-select picklist field to a set, dynamically controlling the size and content of the set based on the picklist options.
Changes to the picklist options directly adjust the set size, offering a streamlined way to manage sets tied to specific selectable options.
Show full answer Show less  
Unlike regular sets where users can add unlimited rows, an associated picklist set generates one row per non-excluded picklist option. Inclusion and exclusion rules can dynamically modify which rows are displayed.

## Key Features

* **Dynamic set sizing:** The set size corresponds exactly to the number of options in the associated multi-select picklist, automatically updating when options are added or removed.
* **Automatic fields creation:** Each associated picklist set generates three fields---Index (row number), Option Value (picklist option value, read-only), and Select Option (Boolean to mark selection).
* **Rule compatibility:** Supports determination, inclusion, and exclusion actions to dynamically control set content, such as removing specific options via rules.
* **Flexible layout placement:** The associated picklist can be positioned anywhere on the page layout, not necessarily next to the set it controls.
* **Integration with picklist extension:** Picklist extension fields can be used as the associated picklist, enabling additional customization.

## Key Outcomes

* **Efficient rule management:** Enables writing a single calculation or action rule applied uniformly across all picklist items, reducing duplication and potential errors.
* **Controlled option usage:** Ideal when each option value should be used only once, allowing precise control over configuration elements such as fees or product quantities.
* **Enhanced user experience:** Users can specify quantities or other details per picklist option in the set, supporting complex scenarios like bill of materials customization.

## Practical Examples

* **Fee calculation:** A multi-select picklist with 100 fees linked to an associated picklist set allows a single rule to calculate each fee's value, ensuring consistency and simplifying maintenance.
* **Product quantity customization:** Using a picklist extension to filter options and an associated picklist set on separate tabs lets users specify quantities for each product added to the bill of materials.  
Learn to use an associated picklist instead of a set field when you create a new set.  
Note:  
Be sure to read about product pickers and their functionality before building associated picklists, as they may be better suited to your use case. See [Product pickers](https://servicenow-prod.fluidtopics.net/Dc9Lu5nMSvLJIXMPr0EAeA "Learn how to create and configure product pickers to add products to a bill of materials (BOM) without writing rules. Define product options, subfields, aggregates, and display settings to enhance user interactions, automate data mapping, and present product information directly in layouts.").

The New Set dialog box includes an option for size type. Set Field is the default. If you select Associated picklist, a new field appears where you can select the picklist field that
will be associated with the set.


This associated picklist must be a multi-select picklist field. This field determines the size of the set based on the number of field options in the picklist. If you edit the field to add or remove field options, the set size will
adjust accordingly. This is the only way to adjust the size of the set associated with the picklist.

For example, a "Condiments" picklist could let users choose to include specific condiments, such as ketchup, mustard, or relish. A "Packets" associated picklist set could then let users specify the quantity of each item using set
subfields.

Unlike a regular set where a user can add as many rows as they want, each non-excluded field option of a picklist generates a row and index of the set. Inclusion and exclusion rules still work on the associated field, which can
dynamically change the number of rows in the associated picklist set. The following is the sample picklist field we will use in this example. (Note that the labels and values differ.)


Once we select Condiments as the associated picklist, the normal set UI appears. Associated picklist sets automatically create three fields in the set:

* Index: the row number of the set, starting at 1
* Option Value: the associate picklistʼs field option values
* Select Option: a Boolean field to indicate that the set index is selected

{#creating_an_associated_picklist_set__ul_rq4_rkr_chc}


Like all other fields in the set, the option value, the select option, and the set itself need to be added to the layout. The following image shows the interaction between the Condiments associated picklist and the packets set:


Note that the option values in the set reflect the associate picklistʼs field option values. ("Ketchup" is reflected as "K", the field option value.) Also note that option values are read-only and cannot be edited.

Associated picklist sets can still be acted upon with determination actions, inclusion actions, and exclusion actions. In the example below, a new field called KetchupBan removes Ketchup as a value from the Condiments picklist:


## Benefits of the associated picklist set {#creating_an_associated_picklist_set__benefits_of_the_ap_set}

Depending on the configuration, there may be several reasons why an associated picklist set would be better than a regular set.

* Situations where each option value can only be used once
* Situations where select Option and Option Value fields that are used for index specific actions and other rules
* Associated picklist sets have a finite size, with as many indexes as the picklist has field options

{#creating_an_associated_picklist_set__ul_aq4_ykr_chc}

Note that picklist extension fields can also be used as the associated picklist. Furthermore, the associated picklist can live elsewhere on the page layout or in the background---it does not need to be near the set it controls.

## Example: A complex rule {#creating_an_associated_picklist_set__section_urm_lqj_shc}

The customer has 100 different fees that could be applied to the configuration. To determine the value of these fees, each fee is calculated using a complex formula. Each fee is only be applied once. The formula is the same for all
fees. The customer does the following in ServiceNow CPQ:

* Creates a multi-select picklist field called Fees with 100 field options (one for each fee)
* Creates an associated picklist set and selects Fees as the associated picklist
* Creates inclusion rules for the Fees field
  * This would create an inclusion rule for each fee based on the condition of that fee.
  * This would also create an inclusion rule that included none of the fees as a default. This way, the Fees are added, as inclusion rules are additive.
  {#creating_an_associated_picklist_set__ul_jtb_qlr_chc}
* Creates a rule for calculating the feeThis is where the associated picklist set is really beneficial. The customer only has to write 1 rule, and it is applied to each row of the set. If the customer did not use the set, they
  would have had to replicate this script multiple times in multiple rules throughout the configuration. This can lead to errors downstream when the complex calculation changes.

{#creating_an_associated_picklist_set__ul_of5_nlr_chc}

## Example: Picklist extension with varying quantities for product rules {#creating_an_associated_picklist_set__section_z2v_mqj_shc}

Another customer has effectively used the picklist extension to filter field options and provide columns of extra information. However, they cannot use the picklist extension to add products to the bill of materials because they
want to give the end user the ability to specify the quantities as each field option is added to the BOM.

They put the picklist extension grid on a single tab tier, and then they put the set, which shows all the field options selected on the first Tab Tier, on the second tab tier. Using the associated picklist set, the end user can
customize for each customer the quantity added to the BOM.

