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


---

# Sets

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

Sets in ServiceNow CPQ are reusable, repeatable groups of configuration fields designed to organize and simplify complex configurations involving multiple similar items, such as products or components.
Each row in a set represents an independent instance of the repeated group of fields, allowing administrators to efficiently manage tabular or list-based inputs in a single blueprint.
Sets reduce duplication, streamline configuration design, and support advanced use cases like dynamic rules and data aggregation.
Show full answer Show less  

## Key Features

* **Repeatable Configurations:** Define configuration fields once and reuse them multiple times, avoiding the need to create separate fields and rules for each repetition.
* **Intuitive Data Entry:** End users interact with structured, table-like or card-based layouts to add, edit, or remove multiple instances easily.
* **Dynamic Rules Support:** Rules can reference values within the same row or aggregate data across all rows to influence configuration behavior.
* **Advanced Reporting and Aggregation:** Aggregate functions (sum, count, average, max, min) enable summarizing values across rows, useful for totals like quantities or rack units.
* **Multiple Display Options:** Sets can be displayed as tables (detailed grid), lists (row cards), or repeaters (one record at a time) depending on user experience needs.
* **Field Relationship Constraints:** Fields can interact within the same row but cannot directly affect fields in other rows; interactions between inside and outside sets require aggregates or product rules.
* **Configurable Properties:** Administrators can customize orientation, height, alignment, display types, inline controls, sizing methods, selection modes, search capabilities, and message displays.
* **Data Management via CSV:** Sets support importing and exporting data in CSV format, allowing bulk updates or downloads of filtered data, with automatic rule execution on uploads.
* **Scripting Access:** Sets and their aggregate fields can be accessed in rules or scripts using a defined syntax, enabling conditional logic based on aggregated set data.

## Key Outcomes

* **Simplified Configuration Management:** Easily handle multiple similar configuration items without redundant field creation.
* **Improved End-User Experience:** Provide clear and manageable interfaces for configuring repeated items, enhancing usability and reducing errors.
* **Enhanced Rule and Reporting Capabilities:** Use aggregated data from sets to drive dynamic product rules and generate meaningful summaries.
* **Efficient Data Handling:** Leverage CSV import/export to maintain large sets of configuration data efficiently and reliably.  
Learn how sets organize repeatable field groups, simplify complex configurations, and enable data aggregation across repeated elements in ServiceNow CPQ.
A set is a reusable, repeatable collection of fields that lets administrators define multiple instances of similar configuration data---such as multiple products, components, or options---in a single blueprint.

Each row in a set represents one instance of a repeated group of fields, and each field in that row behaves independently. sets streamline configuration design, reduce duplication, and support advanced use cases that require tabular
or list-based inputs.

Administrators use sets to present configuration options in structured, table-like layouts that customers can easily edit in the end-user interface.  
Sets are designed to:

* Simplify repeatable configurations. Instead of creating multiple fields and rules for each repetition, define once and reuse many times.
* Provide intuitive, tabular data entry. End users can add, remove, or edit multiple product instances in a structured grid.
* Support dynamic rules. Rules can reference values in the same row or aggregate data across all rows.
* Enable advanced reporting and summaries. Aggregates summarize field values across rows (for example, total quantity or total rack units).
{#cpq-sets__ul_qgd_5yb_hhc}

## How sets work {#cpq-sets__section_yzn_wyb_hhc}

A set groups several configuration fields together and repeats that group for each item in the list.  
Each set row is fully independent:

* Fields in the same row can affect other fields in that row.
* Fields in one row cannot directly affect fields in another row.
* Fields outside a set can influence fields inside it, but not vice versa.
{#cpq-sets__ul_e5b_xyb_hhc}

To affect fields outside a set, use:

* Aggregates: Sum, count, average, maximum, or minimum values across all rows.
* Product rules: Define logic that sets external field values based on set data.

{#cpq-sets__ul_f5b_xyb_hhc}

A set can contain up to 2,000 rows.

## Display options {#cpq-sets__section_dhm_zyb_hhc}

Sets can appear in the UI in several formats, depending on user experience requirements:
{#cpq-sets__table_g42_1zb_hhc__entry__3}

| Display type | Description | Example use case |
|-|-|-|
| Table | Rows, columns, and cells with headers; ideal for detailed comparisons. | Configure multiple network devices. |
| List | Each row shown as a card; can support single-select or multi-select. | Select delivery slots or service packages. |
| Repeater | Displays one record at a time with navigation controls. | Edit configurations one-by-one in smaller layouts. |
[Table 1. Display options for sets]

{#cpq-sets__table_g42_1zb_hhc}

Administrators control layout, alignment, and scrolling in the layout editor.

## Field relationships {#cpq-sets__section_bvp_bzb_hhc}

{#cpq-sets__table_kw3_czb_hhc__entry__2}

| Relationship | Behavior |
|-|-|
| Inside → Inside | Fields in the same row can trigger each other through rules. |
| Inside → Outside | Not allowed directly; use Aggregates or Product Rules. |
| Outside → Inside | Allowed. Rules or field actions outside a set can change set field values. |
[ ]

{#cpq-sets__table_kw3_czb_hhc}

## Key properties {#cpq-sets__section_ukk_fzb_hhc}

Sets include several configuration categories that shape how users interact with the table or list:

* General settings: Orientation, maximum height, alignment, index labels.
* Display type: Choose between Table and List views.
* Inline settings: Show "Add Row" indicators, drop-down controls, or hover actions.
* Size settings: Manage how users increase or decrease set rows (numeric or slider field).
* Selection settings: Add single or multiple row selection with a Boolean selection field.
* Search settings: Allow users to search values in a set (for example, filter by available date).
* Message settings: Display validation messages or indicators in specific cells.
{#cpq-sets__ul_vmf_gzb_hhc}

## Managing set data {#cpq-sets__section_brr_hzb_hhc}

Sets support importing and exporting data in CSV format.

* Download set data: Exports only visible columns based on filters applied in the UI.
* Upload set data: Adds or updates rows in the set using a structured CSV file.
  * Rules run automatically on upload.
  * New rows are appended; matching rows are updated.
  * System-enforced limits apply (25 visible columns recommended).
  {#cpq-sets__ul_py1_mzb_hhc}

{#cpq-sets__ul_oy1_mzb_hhc}  
Enable uploads/downloads by adding JSON properties in the set's raw value:

    {
      "uploadDetails": {
        "uploadButton": { "label": "Upload CSV", "visible": true },
        "downloadButton": { "label": "Download CSV", "visible": true }
      }
    }

## Scripting with sets {#cpq-sets__section_ug3_pzb_hhc}

To reference sets in rules or scripts, use the following syntax:
{#cpq-sets__table_xs3_qzb_hhc__entry__2}

| Use case | Example syntax |
|-|-|
| Access the set | `set.<setVarName>` |
| Access an aggregate field | `set.<setVarName>.<aggregateVarName>` |
[ ]

{#cpq-sets__table_xs3_qzb_hhc}  
For example:

    if (set.networkDevices.totalRackUnits > 50) {
       field.requiresAdditionalCooling = true;
    }

**Related concepts**   

* [Configure sets](https://servicenow-prod.fluidtopics.net/8jwHVPucTAm3wJqGdJ95KQ "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.")

