Overview
The Tab Bar row type creates a set of tabs within a column, each containing its own set of rows. This allows you to nest additional levels of tabbed organisation within an existing panel, providing a compact way to present multiple views or data sets without using additional top-level panel tabs.
When to Use
Use the Tab Bar row type when you need to:
- Organise multiple related sections within a single panel without creating separate top-level tabs
- Present different views of related data in a compact space
- Reduce the number of top-level panels while still providing structured access to information
- Create sub-navigation within a column
Properties
| Property | Required | Description |
|---|---|---|
| Type | Yes | Must be set to tabbar |
| Tabs | Yes | An array of tab definitions. Each tab contains an ID, display name, and an array of rows. |
Tab Definition Structure
Each entry in the Tabs array has the following properties:
| Property | Description |
|---|---|
| ID | A unique identifier for the tab |
| Tab | The display name shown on the tab button |
| Rows | An array of row definitions that appear when this tab is selected. These follow the same structure as rows in a column — each can be a form, related list, object array, or any other row type. |
How It Works
When the record is opened, the Tab Bar displays a row of tab buttons. Clicking a tab shows the rows defined for that tab and hides the others. This works similarly to the top-level panel tabs but operates within a column rather than across the entire record.
Nesting Capabilities
The rows within each tab can be any supported row type. This means you can nest forms, related lists, object arrays, dashboards, and any other row type within a Tab Bar tab. This provides powerful compositional flexibility.
Best Practices
- Use Tab Bar when you have 2 to 5 related sections that would otherwise clutter a single column
- Keep tab names short (one or two words) as they share horizontal space
- Avoid deeply nesting Tab Bars within Tab Bars, as this can create a confusing user experience
- Consider whether top-level panels might be more appropriate for distinct categories of information
Example Uses
- A "Details" tab and a "History" tab within a sidebar column, while the main column shows a dashboard
- "Budget", "Actuals", and "Forecast" tabs within a financial section
- "Internal" and "External" tabs for different stakeholder views of the same record