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


---

# Multi-tier structure (nested tiers)

# Multi-tier structure (nested tiers) {#ariaid-title1}

Release version: Brazil  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 Multi-tier structure (nested tiers)

ServiceNow CPQ enables the creation of complex, multi-tier layouts by nesting tiers within other tiers using a layout CSV file.
This functionality helps organize configuration interfaces with flexible, structured, and visually clear presentations using tier display types such as tabs, expandable sections, and basic containers.
The focus is on the top-level container called tiers, which can be nested to create sophisticated layouts.
Show full answer Show less  

## Key Features

* **Tier Types:** Two basic container types exist---tiers and column sets---with tiers being the primary container for nesting.
* **Display Types:** Tiers can use various display types including tabs, expandable sections, vertical tabs, and basic containers to organize fields effectively.
* **Nesting Capability:** Multi-level nesting is supported by defining nested tiers in the CSV layout file, allowing deep, hierarchical configurations.
* **CSV Layout Structure:** The tier definition in the CSV controls the visual display for all tiers at that level, not just a single tier. Nested tiers are specified by paths such as "layout/tiers/tiers" for tiers inside other tiers.
* **Display Type Restrictions:** Multiple tier definitions at the same hierarchy level with different display types are not supported; only one display type per level is valid.
* **Fields Outside Bottom Tier:** To display fields outside a nested bottom tier, an intermediary tier with the BasicContainer display type can be used to separate layers.
* **Layout Editor Limitations:** As of May 23, 2023, nesting tiers cannot be created or modified directly in the Layout Wizard or layout editor, but existing nested tiers' display types can be changed.

## Practical Application for ServiceNow Customers

This multi-tier nesting capability allows ServiceNow CPQ users to design advanced product configuration interfaces that are logically structured and user-friendly. By leveraging nested tiers, customers can:

* Create tabbed or expandable sections to group related configuration fields.
* Build complex layouts with multiple levels of detail and organization.
* Maintain clarity and usability in product configuration forms by selecting appropriate tier display types.
* Present some fields outside deeply nested tiers using basic containers for better context.

Understanding the CSV layout format and tier path conventions is essential for implementing these structures. Customers should plan tier display types carefully to avoid invalid configurations and expect to manage nested tiers primarily through CSV files rather than the UI layout editors currently.  
Create complex, multi-tier layouts in ServiceNow CPQ by nesting tiers in other tiers using a layout CSV file. Define tier display types---such as tabs, expandable sections, and basic containers---to organize fields and achieve flexible, structured, and visually clear
configuration interfaces.
In ServiceNow CPQ, there are two basic container types: tiers and column sets. This article focuses on the top-level container (tiers) and how to achieve more complex layouts by nesting different types of tiers.  
Note:  
As of May 23, 2023, nesting tiers is not supported in the Layout Wizard or in the layout editor. However, you can change the display type of existing tiers, including nested tiers.

The basic CSV format for a single-tier structure looks like this:


The tier definition defines the visual display of a level of tier, not just one particular tier. So in this case, all three tiers (tab1, tab2, and tab3) are defined as the Tab display type. This creates a simple structure where
each tier in the CSV file appears as a tab.

However, different types of tier display types may sometimes be nested in another tier. The simplest example is a two-tier structure. Letʼs build off of our first example and nest some expandable sections in one of our tabs.


Notice how the nested tier is defined. The tier definition row path is "layout/tiers/tiers", indicating that a tier that is below another tier in the path should be defined as an expandable section. You can then see that on rows 3
and 4, the tier "exsect1" is placed below the tier "tab1" in the path. This displays for the end-user like so:


You can extrapolate this pattern to create deeper tier structures, declaring more and more nested definitions. However, note that you cannot have multiple tier definitions at the same level. For example, the tiers in the first
image shown below are valid, but the tiers in the second image are not valid, because the component display type for /layout/tiers/tiers is both ExpandableSection and VerticalTab.

Valid tiers:

Invalid tiers:


## Displaying fields outside the bottom tier {#layout_multi-tier_structurenested_tiers__displaying_fields_outside_of_the_bottom_tier}

A common use case of nested tiers may be to have a bottom layer nested inside a top layer tier, with some general fields displayed outside the bottom tier. This can be achieved by using an intermediary tier of the BasicContainer
display type. This structure might look like this for the end user:


The layout CSV file is structured like so:


