---
sourceDocument: Australia Sales and Order Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/order-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Sales and Order Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# Sets

# Sets {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 Minuten Lesedauer

Learn how sets organize repeatable field groups, simplify complex configurations, and enable data aggregation across repeated elements in 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. |
[Tabelle : 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;
    }

**Zugehörige Konzepte**   

* [Configure sets](https://servicenow-prod.fluidtopics.net/plljw~DTzPPFMOddSu~hhw "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 CPQ.")