--- 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 --- # Configure sets # Configure 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 Configure sets Configure sets in ServiceNow CPQ enable administrators to group related fields into repeatable collections, streamlining configurations and reducing redundancy. Sets allow dynamic, table-like data entry, support aggregates, and simplify managing repeated questionnaires or configurable options. They help reduce the number of fields and rules needed for use cases involving repeated data groups. Show full answer Show less Administrators can create sets containing multiple fields that end users can replicate multiple times (up to 2000 records) within the UI in various display formats such as table rows, table columns, list rows, or set repeaters. ## Key Features * **Repeatable Groups:** Fields grouped in sets can be repeated indefinitely, supporting flexible data entry. * **Display Types:** Sets can be presented as table rows, columns, lists, or repeaters to best fit the UI needs. * **Set Management:** Users can add or remove set records via UI controls including buttons, size fields, and index column menus. * **Creation and Configuration:** Sets are created within blueprints or the fields administration tab by selecting the set field type and defining the size type (fixed numeric or associated picklist). * **Associated Picklist Sets:** When using this type, ServiceNow CPQ automatically adds fields to track option values and selections. * **Distinct Values Enforcement:** Fields within a set can be configured to require unique values per record, improving data integrity. * **Aggregates:** Sets support aggregate functions (Average, Count, Maximum, Minimum, Sum) on fields, enabling calculations across repeated records and integration with global rules. ## Practical Use and Considerations Sets are ideal for scenarios requiring repeated, structured data input such as configurable product options or questionnaires. Administrators should carefully choose the size type during set creation since it cannot be changed later. Understanding how sets interact with blueprints and rules is important for effective configuration and ensuring correct behavior within the CPQ system. Management of sets is facilitated by the Layout Wizard, and additional guidance on using sets in layouts and their interaction with blueprints is available for administrators implementing these features. 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://www.servicenow.com/docs/17K2GGeLU_zYvXa9Taf~JA "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://www.servicenow.com/docs/17K2GGeLU_zYvXa9Taf~JA "Learn about the various ways sets can be displayed and about their settings.") and [How sets interact with the rest of a blueprint](https://www.servicenow.com/docs/AE~yVtp1EIJ9~issfXx1ug "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://www.servicenow.com/docs/S51g6w__JpaODZKB8nMRGg "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://www.servicenow.com/docs/wnTk5LfVeuIEUSab4eSvBQ "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://www.servicenow.com/docs/AE~yVtp1EIJ9~issfXx1ug "The implications of sets when used in blueprints."). **Related concepts** * [Using sets in layouts](https://www.servicenow.com/docs/17K2GGeLU_zYvXa9Taf~JA "Learn about the various ways sets can be displayed and about their settings.")