Grid-style fields and field collections
Summarize
Summary of Grid-style fields and field collections
This guide introduces various grid-style fields in ServiceNow's CPQ, including picklist extensions, field grids, indexed sets, associated picklist sets, and product pickers. Each field type serves distinct purposes and behaviors for admins while appearing similar to end users. Understanding these differences is essential for effectively managing data input and display.
Show less
Key Features
- Picklist Extension: Displays extended information, allows multi-select/single-select actions, includes images, and integrates with the BOM. It uses exclusion rules and option filters for user visibility.
- Field Grid: Organized in rows and columns, suitable for static displays of interrelated fields. Each field is independently defined and can be manipulated by rules.
- Indexed Set: A dynamic collection of identical fields that can be customized per component, requiring minimal setup. Fields can be cloned and edited based on external numbers, with aggregations possible across columns.
- Associated Picklist Set: Similar to indexed sets but based on picklist options, useful for aggregating costs and limiting configurable options.
- Product Picker: A product-focused table that collects distinct user inputs before adding items to the BOM, with defined options and automatic inclusion of value, select, and quantity fields.
Key Outcomes
By understanding and utilizing these grid-style fields effectively, ServiceNow customers can enhance data entry processes, improve user experience, and drive accurate configuration management in their applications. Each field type is designed to address specific data management needs, streamlining operations and ensuring better control over product configurations.
Learn about the various types of grid-style fields: the picklist extension, the field grid, the indexed set, the associated picklist set, and the product picker. Learn how best to choose a field type for your data.
In CPQ, although many grid-style fields and field collections look similar to an end user, they have different behaviors and uses for admins. This article explains the basic capabilities of each and their intended use cases. It also provides the necessary resources for those who want to explore each option’s setup at a deeper level.
Picklist extension
A picklist extension is a field type that displays extended information. It may be used to show more option details or to show dynamic pricing options with the Picklist Extension Pricing enrichment. A picklist extension can include images and supports multi-select and single-select actions. It can send product information directly to the bill of materials (BOM).
A picklist extension uses exclusion rules and option filters to populate what end users see. Only one field is editable out of the grid (the selection).
For an overview of the picklist extension feature, see Picklist extensions.
For a deeper understanding of the back end and how to display picklist extensions, see Displaying a picklist extension on a layout.
For an overview of the Picklist Extension Pricing enrichment feature, see The Picklist Extension Pricing enrichment.
For information about using picklist extensions in rules, see Picklists and picklist extensions in rules.
Field grid
A field grid is a grid of independent fields in a format of rows and columns. It may be used to display similar and codependent fields in an easy-to-format pattern, when the number of fields to display is static, or when each field needs to be referenced outside of its own row and column.
Each field can be referenced and manipulated by any rule and must be independently defined. For example, a 3 x 3 row requires 9 fields.
For information about how to set up a field grid using the Matrix Loader, see Layouts: Field grid setup.
Indexed set
An indexed set is a dynamic set of repeating identical fields. It can be used to display options for a component that can be changed per component, or to aggregate costs and quantities for simple product rules. It tends to require little setup and maintenance.
Each field can be cloned and edited separately depending on an outside number field. You only need to create the fields in each row, not one field per cell.
Each set field can only affect the fields in its row.
Each column can be aggregated into a field that can be referenced outside the set. It can be configured to display across tiers.
For more information about sets, set aggregates (collections of sets) and about how to use sets in layouts, see:
Associated Picklist set
An Associated Picklist set is a dynamic set of repeating fields based on the options of a picklist. It may be used to aggregate costs and work hours for distinct services, to limit the options of a configurable component, or to expand and use more field options for a picklist than a picklist extension.
Each field can be cloned and edited separately depending on an outside picklistʼs selections. You only need to create the fields in each row, not one field per cell.
Each set field can only affect the fields in its row.
Each column can be aggregated into a field that can be referenced outside the set. It can be configured to display across tiers.
For more information, see Creating an associated picklist set.
Product Picker
The product picker field type is a product-based table of distinct options and qualities similar to the Associated Picklist set, but with built-in product rules. It may be used when product options need further information from the end user before being added to the BOM.
Each option is defined like a picklist, but every cell contains an editable field. You only need to define the options and fields, as shown in the row and column headers.
Value, Select, and Quantity are automatically added, and will automatically send end-user selections to the BOM. Field behavior in a product picker is determined by product picker bulk actions.
This field can affect fields outside the product picker by means of rules.
For more information, see: