> ## Documentation Index
> Fetch the complete documentation index at: https://docs.omni.co/llms.txt
> Use this file to discover all available pages before exploring further.
## Submitting Feedback
If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:
POST https://docs.omni.co/feedback
```json
{
"path": "/guides/modeling/nested-field-groups",
"feedback": "Description of the issue"
}
```
Only submit feedback when you have something specific and actionable to report.
# Organize fields with nested groups
> Keep workbook field browsers navigable by grouping related fields.
export const categoryIcons = {
'administration': 'lock',
'api': 'terminal',
'connections': 'database',
'dashboards': 'table-columns',
'embed': 'code',
'errors': 'exclamation',
'modeling': 'wrench',
'patterns': 'plus',
'schedules & alerts': 'envelope',
'visualizations': 'chart-column',
'workbooks': 'book'
};
export const GuideSidebar = ({category, relatedLinks, updatedDate}) => {
const [progress, setProgress] = React.useState(0);
React.useEffect(() => {
const sidebar = document.querySelector('.guide-sidebar');
if (!sidebar) return;
let container = sidebar.parentElement;
while (container && !container.querySelector('.guide-header')) {
container = container.parentElement;
}
if (container && !container.classList.contains('guide-page-layout')) {
container.classList.add('guide-page-layout');
}
}, []);
React.useEffect(() => {
const handleScroll = () => {
const scrollTop = window.scrollY;
const docHeight = document.documentElement.scrollHeight - window.innerHeight;
const scrollPercent = docHeight > 0 ? scrollTop / docHeight * 100 : 0;
setProgress(Math.min(100, Math.max(0, scrollPercent)));
};
window.addEventListener('scroll', handleScroll, {
passive: true
});
handleScroll();
return () => window.removeEventListener('scroll', handleScroll);
}, []);
const icon = category ? categoryIcons[category.toLowerCase()] || 'book' : 'book';
return ;
};
export const GuideTitle = ({title}) => {
return
{title}
;
};
Grouping related fields together ensures that the field browser in workbooks is tidy and easily navigable.
## Limitations
**[Dimensions](/modeling/dimensions) and [measures](/modeling/measures) can't be grouped together.** Applying the same group label to a dimension and a measure will result in two groups displaying in the field browser, not one group with both fields.
## Group creation
Group structures are created by using the greater-than symbol (`>`) in a dimension or measure `group_label` parameter, which must have whitespace on either side. Each segment will become a collapsible group level in the field browser.
For example, to create the following structure in the field browser:
```markdown title="Field browser structure for Location group" theme={null}
▾ Location
▾ Address
street_address
city
▾ Coordinates
latitude
longitude
```
You would add the following `group_label` parameters to the `street_address`, `city`, `latitude`, and `longitude` dimensions:
```yaml title="Create a Location group with Address & Coordinates subgroups" theme={null}
dimensions:
street_address:
group_label: Location > Address
city:
group_label: Location > Address
latitude:
group_label: Location > Coordinates
longitude:
group_label: Location > Coordinates
```
This example used dimensions, but you can also create group structures for measure fields the same way. Nested groups are especially helpful for measures that answer the same question in slightly different ways, as it lets you start broad and drill into more specific definitions only when needed.
Aggregation types have been omitted in the following example to keep the focus on group creation.
```yaml title="Grouping measures in a support_tickets view" theme={null}
measures:
first_response_breach_by_day:
group_label: SLA breaches > First response
first_response_breach_by_month:
group_label: SLA breaches > First response
breach_resolution_by_day:
group_label: SLA breaches > Resolution
breach_resolution_by_month:
group_label: SLA breaches > Resolution
```
Which will create the following structure in the field browser:
```markdown title="Field browser structure for SLA breaches group" theme={null}
▾ SLA breaches
▾ First response
first_response_breach_by_day
first_response_breach_by_month
▾ Resolution
breach_resolution_by_day
breach_resolution_by_month
```
## Nesting depth
Groups can be nested:
```yaml theme={null}
dimensions:
detailed_address:
group_label: Geography > Location > Address > Details
```
```markdown theme={null}
▾ Geography
▾ Location
▾ Address
▾ Details
detailed_address
```
## Field browser collapse and expand behavior
Field groups will behave as follows:
* **Click a group header** to expand or collapse its contents
* **Nested groups** only appear when their parent group is expanded
* **Fields** only appear when all ancestor groups are expanded
* When you **select or filter** a field, its parent groups show an indicator so you can see which groups contain active selections even when collapsed