---
sourceDocument: Australia Sales Customer Relationship Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/order-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Sales Customer Relationship Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# Sets

# Sets {#ariaid-title1}

Release version: Australia  
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 provide a powerful way to organize repeatable groups of fields, enabling administrators to define multiple instances of similar configuration data within a single blueprint.
This feature simplifies complex configurations by allowing repeatable collections of fields---such as products or components---to be managed as tabular or list-based inputs, streamlining configuration design and reducing duplication.
Show full answer Show less  
Each row in a set represents an independent instance of the group of fields, allowing end users to easily add, edit, or remove items through an intuitive, table-like interface. Sets also support dynamic rules and aggregated data, which help enable advanced configurations and reporting.

## Key Features

* **Repeatable Configurations:** Define groups of fields once and reuse them multiple times without duplicating configurations.
* **Intuitive Data Entry:** Provide customers with structured, editable grids or card-like lists to manage multiple instances of configuration data.
* **Dynamic Rules Support:** Rules can interact with fields within the same row and aggregate data across rows, enabling complex logic.
* **Advanced Reporting and Summaries:** Aggregate functions like sum, count, average, max, and min help summarize data across all rows for actionable insights.
* **Multiple Display Types:** Sets can be displayed as tables, lists, or repeaters to fit different user experience needs.
* **Configurable Properties:** Customize general settings, inline controls, size adjustments, selection options, search capabilities, and validation messages for a tailored experience.
* **Data Management:** Import and export set data using CSV files, with automatic rule execution on uploads and system limits to ensure performance.
* **Scripting Access:** Use straightforward syntax to reference sets and aggregates within rules and scripts for enhanced automation and control.

## How Sets Work

Sets group multiple configuration fields into repeatable rows, each functioning independently. Fields within the same row can trigger rules that affect one another, but do not directly impact fields in other rows. Fields outside the set can influence fields inside it, but not vice versa, except through aggregates or product rules.

An example use case includes configuring multiple network devices in a table format or selecting service packages through a card-based list view. Sets can handle up to 2,000 rows, offering ample scale for complex configurations.

## Practical Benefits for ServiceNow Customers

* Streamline product or service configurations with reusable, repeatable field groups.
* Enhance end-user experience by providing clear, editable tables or lists for configuration inputs.
* Implement dynamic pricing, validation, or conditional logic based on aggregated or row-specific values.
* Enable efficient bulk data updates through CSV import/export capabilities.
* Leverage scripting support for customized automation and integration with other configuration elements.  
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://www.servicenow.com/docs/R63loIv9IqhXYdnJheZV4w "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.")