---
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


---

# Configure sets

# Configure sets {#ariaid-title1}

Release version: Brazil  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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 Configure sets

Sets in ServiceNow CPQ allow administrators to group related fields into repeatable collections, enabling dynamic, table-like data entry.
This reduces redundancy by minimizing the number of fields and rules needed for repeated use cases, such as questionnaires or configurable options.
Sets can be repeated up to 2000 times, streamlining complex configurations and simplifying management.
Show full answer Show less  

## Key Features

* **Flexible Display Types:** Sets can be presented as table rows, table columns, list rows, or set repeaters, providing adaptable UI options.
* **Record Management:** End users can add or remove set records through multiple UI controls, including buttons, size fields, index column controls, and menus.
* **Creation and Configuration:** Sets are created within blueprints or the fields administration tab by selecting the set field type and naming the set. Size types are fixed upon saving and determine how many records display, either via numeric fields or associated picklists.
* **Associated Picklist Sets:** When chosen, two extra fields are created---Option Value (read-only) and Select Option (tracking selection)---to manage picklist-driven set sizes.
* **Field Management within Sets:** Administrators can add fields to sets, enforce distinct values for specific fields to ensure uniqueness, and create aggregates such as Average, Count, Maximum, Minimum, and Sum.
* **Aggregates:** Aggregates act as external fields summarizing data from the set and can be utilized in global rules for further automation and logic.
* **Layout Integration:** Sets are manageable via the Layout Wizard, allowing seamless integration into user interfaces.

## Practical Considerations

* The fixed size type of a set field influences how many repeated records appear and whether users can edit this count.
* Distinct value enforcement applies only to non-empty fields within the set, ensuring data integrity.
* Understanding how sets interact with blueprints and rules is crucial for effective configuration and rule creation.

## Next Steps for Customers

To implement sets effectively, use the Layout Wizard to manage their appearance and behavior in your configurations. Leverage aggregates to summarize repeated data points and maintain data uniqueness with distinct values. Consider associated picklist sets when you need dynamic control over the number of set records based on picklist options. Review how sets interact with global rules and blueprints to optimize your CPQ configurations.  
Sets group related fields into repeatable collections, allowing administrators to streamline configurations and reduce redundancy. They enable dynamic, table-like data entry, support aggregates, and simplify managing repeated
questionnaires or configurable options in ServiceNow CPQ.
[Sets introduction](https://www.youtube.com/watch?v=1Wt_GYaSr7Y&t=2s)

Sets allow the administrator to identify a number of fields in a group. Once associated with a set, the fields may then be replicated an indefinite number of times on the end-user UI in a matrix format. Sets reduce the number of
fields and rules that must be defined for use cases that repeat fields and rules. The maximum number of set records (the number of times a group of fields can be repeated) is 2000.

In this set, three fields (Sandwich Choice, Side Choice, and Drink Choice) are defined in a set; the set is repeated three times:

## Display types {#sets__section_jft_klq_chc}

Sets can be displayed in several ways.

* As table rows:

* As table columns:

* As list rows:

* As a set repeater:

{#sets__ul_d4m_nmq_chc}

You can manage sets by using the Layout Wizard. For more information about sets and layouts, see [Using sets in layouts](https://servicenow-prod.fluidtopics.net/UnnWkFcJ3wOBZkvg5OYXIg "Learn about the various ways sets can be displayed and about their settings.").

## Adding and removing set rows {#sets__section_edh_llq_chc}

In the end-user UI, the user has four ways to increment or decrement set records:

* To add a record to the bottom of the set, click the green plus in the upper right corner.

* To add or remove records from the bottom of the set, edit the Size field and click Change Size.

* To insert a record between two existing records, hold the cursor between them in the Index column.

* To add records relative to the current record or to delete a record, use the menu in the Index column.

  For more information about managing sets, see [Using sets in layouts](https://servicenow-prod.fluidtopics.net/UnnWkFcJ3wOBZkvg5OYXIg "Learn about the various ways sets can be displayed and about their settings.") and [How sets interact with the rest of a blueprint](https://servicenow-prod.fluidtopics.net/xjh4bnAHM6rpcRdAq3xasw "The implications of sets when used in blueprints.").
{#sets__ul_twd_vmq_chc}

## Creating a set {#sets__section_alz_llq_chc}

Sets can be added in the same two areas you would create fields: the blueprint to which to add the set, and the fields administration tab.

Select the set field type from among the list of options:

Give your new set a name and choose from the size types.

The size type cannot be changed after the set is saved. Therefore, keep the following in mind:

* The set field determines the number of records that will be displayed in the set. This numeric field can be visible and edited by a user or set by determination action, as the case requires.
* The associated picklist leverages a picklist field to determine how many records to show in the set. When this option is selected, the admin must identify the field that will drive the set size. When the set type is Associated Picklist, ServiceNow CPQ creates two additional fields in the set:
  * Option Value: The value of each option in the set, represented as a read-only text field.
  * Select Option: Tracks whether each option of the picklist is selected.
  * 

  {#sets__ul_y2p_snq_chc}

  For more information, see [Creating an associated picklist set](https://servicenow-prod.fluidtopics.net/SVtAQMXH6Bw4agl0~3Kz2g "Learn to use an associated picklist instead of a set field when you create a new set.").

{#sets__ul_xbx_hnq_chc}

The next screen is the set screen, where the admin can add fields to the set, enforce distinct values, and create aggregates.

To add a field to the set, search for the name of the field to be added to the set, and then click +.

Any field in the set can have the "Distinct Values" option enabled. When this is true, each index of the set must have a unique value for the field. This setting only applies to non-empty fields.

When you create an aggregate for a field in the set, options include Average, Count, Maximum, Minimum, and Sum. For example, a sum aggregate on a number field called Quantity might store the sum of all Quantity field values in the
set. Aggregates function as a field external to the set and can be used in global rules.

For more information on set aggregates, see [Creating set aggregates](https://servicenow-prod.fluidtopics.net/9ehjK~dbVAZZEJn5Gc8h2Q "You can collect the average, count, maximum, minimum, and sum of the data in any field in a set by using a set aggregate.").

When using sets in a configuration, it's important to understand the scope of fields in the set and what can and cannot be accomplished when creating rules. See [How sets interact with the rest of a blueprint](https://servicenow-prod.fluidtopics.net/xjh4bnAHM6rpcRdAq3xasw "The implications of sets when used in blueprints.").
**Related concepts**   

* [Using sets in layouts](https://servicenow-prod.fluidtopics.net/UnnWkFcJ3wOBZkvg5OYXIg "Learn about the various ways sets can be displayed and about their settings.")

