TreeTable is used to display hierarchical data in tabular format.
import { TreeTable } from 'primereact/treetable';
import { Column } from 'primereact/column';
TreeTable requires a collection of TreeNode instances as a value and Column components as children for the representation. The column with the element to toggle a node should have expander enabled.
Name | Size | Type |
|---|
<TreeTable value={nodes} tableStyle={{ minWidth: '50rem' }}>
<Column field="name" header="Name" expander></Column>
<Column field="size" header="Size"></Column>
<Column field="type" header="Type"></Column>
</TreeTable>
Columns can be created programmatically.
Name | Type | Size |
|---|
<TreeTable value={nodes} tableStyle={{ minWidth: '50rem' }}>
{columns.map((col, i) => (
<Column key={col.field} field={col.field} header={col.header} expander={col.expander} />
))}
</TreeTable>
Expansion state is controlled with expandedKeys and onToggle properties. The expandedKeys should be an object whose keys refer to the node key and values represent the expanded state e.g. {'0-0': true}.
Name | Size | Type |
|---|
<Button onClick={toggleApplications} label="Toggle Applications" />
<TreeTable value={nodes} expandedKeys={expandedKeys} onToggle={(e) => setExpandedKeys(e.value)} className="mt-4" tableStyle={{ minWidth: '50rem' }}>
<Column field="name" header="Name" expander></Column>
<Column field="size" header="Size"></Column>
<Column field="type" header="Type"></Column>
</TreeTable>
Custom content at header, body and footer sections are supported via templating. The toggler can be customized with the togglerTemplate property.
Name | Size | Type |
|---|
<TreeTable value={nodes} header={header} footer={footer} togglerTemplate={togglerTemplate} tableStyle={{ minWidth: '50rem' }}>
<Column field="name" header="Name" expander></Column>
<Column field="size" header="Size"></Column>
<Column field="type" header="Type"></Column>
<Column body={actionTemplate} headerClassName="w-10rem" />
</TreeTable>
Pagination is enabled by adding paginator property and defining rows per page.
Name | Size | Type |
|---|
<TreeTable value={nodes} paginator rows={5} rowsPerPageOptions={[5, 10, 25]} tableStyle={{ minWidth: '50rem' }}>
<Column field="name" header="Name" expander></Column>
<Column field="size" header="Size"></Column>
<Column field="type" header="Type"></Column>
</TreeTable>
Paginator UI is customized using the paginatorTemplate property. Each element can also be customized further with your own UI to replace the default one, refer to the Paginator component for more information about the advanced customization options.
Name | Size | Type |
|---|
<TreeTable value={nodes} paginator rows={5} rowsPerPageOptions={[5, 10, 25, 50]}
paginatorTemplate="RowsPerPageDropdown FirstPageLink PrevPageLink CurrentPageReport NextPageLink LastPageLink"
currentPageReportTemplate="{first} to {last} of {totalRecords}"
paginatorLeft={paginatorLeft} paginatorRight={paginatorRight} tableStyle={{ minWidth: '50rem' }}>
<Column field="name" header="Name" expander></Column>
<Column field="size" header="Size"></Column>
<Column field="type" header="Type"></Column>
</TreeTable>
Sorting on a column is enabled by adding the sortable property.
Name | Size | Type |
|---|
<TreeTable value={nodes} tableStyle={{ minWidth: '50rem' }}>
<Column field="name" header="Name" expander sortable></Column>
<Column field="size" header="Size" sortable></Column>
<Column field="type" header="Type" sortable></Column>
</TreeTable>
Multiple columns can be sorted by defining sortMode as multiple. This mode requires metaKey (e.g. ⌘) to be pressed when clicking a header.
Name | Size | Type |
|---|
<TreeTable value={nodes} sortMode="multiple" tableStyle={{ minWidth: '50rem' }}>
<Column field="name" header="Name" expander sortable></Column>
<Column field="size" header="Size" sortable></Column>
<Column field="type" header="Type" sortable></Column>
</TreeTable>
Filtering is enabled by adding the filter property to a Column. The filterMode specifies the filtering strategy, in lenient mode when the query matches a node, children of the node are not searched further as all descendants of the node are included. On the other hand, in strict mode when the query matches a node, filtering continues on all descendants. A general filled called globalFilter is also provided to search all columns that support filtering.
Name | Size | Type |
|---|---|---|
<SelectButton value={filterMode} onChange={(e) => setFilterMode(e.value)} options={filterOptions} />
<TreeTable value={nodes} globalFilter={globalFilter} header={header} filterMode={filterMode} tableStyle={{ minWidth: '50rem' }}>
<Column field="name" header="Name" expander filter filterPlaceholder="Filter by name"></Column>
<Column field="size" header="Size" filter filterPlaceholder="Filter by size"></Column>
<Column field="type" header="Type" filter filterPlaceholder="Filter by type"></Column>
</TreeTable>
Single node selection is configured by setting selectionMode as single along with selectionKeys and onSelectionChange properties to manage the selection value binding.
By default, metaKey press (e.g. ⌘) is necessary to unselect a node however this can be configured with disabling the metaKeySelection property. In touch enabled devices this option has no effect and behavior is same as setting it to false.
Name | Size | Type |
|---|
<InputSwitch checked={metaKey} onChange={(e) => setMetaKey(e.value)} />
<TreeTable value={nodes} selectionMode="single" selectionKeys={selectedNodeKey}
onSelectionChange={(e) => setSelectedNodeKey(e.value)} metaKeySelection={metaKey} tableStyle={{ minWidth: '50rem' }}>
<Column field="name" header="Name" expander></Column>
<Column field="size" header="Size"></Column>
<Column field="type" header="Type"></Column>
</TreeTable>
More than one node is selectable by setting selectionMode to multiple. By default in multiple selection mode, metaKey press (e.g. ⌘) is necessary to add to existing selections however this can be configured with disabling the metaKeySelection property. Note that in touch enabled devices, TreeTable always ignores metaKey.
In multiple selection mode, value binding should be a key-value pair where key is the node key and value is a boolean to indicate selection.
{
'0-0': true,
'0-1-0': true
}
Name | Size | Type |
|---|
<InputSwitch checked={metaKey} onChange={(e) => setMetaKey(e.value)} />
<TreeTable value={nodes} selectionMode="multiple" selectionKeys={selectedNodeKeys}
onSelectionChange={(e) => setSelectedNodeKeys(e.value)} metaKeySelection={metaKey} tableStyle={{ minWidth: '50rem' }}>
<Column field="name" header="Name" expander></Column>
<Column field="size" header="Size"></Column>
<Column field="type" header="Type"></Column>
</TreeTable>
Selection of multiple nodes via checkboxes is enabled by configuring selectionMode as checkbox.
In checkbox selection mode, value binding should be a key-value pair where key is the node key and value is an object that has checked and partialChecked properties to represent the checked state of a node.
{
'0-0': {
partialChecked: false,
checked: true
}
}
Name | Size | Type |
|---|
<TreeTable value={nodes} selectionMode="checkbox" selectionKeys={selectedNodeKeys}
onSelectionChange={(e) => setSelectedNodeKeys(e.value)} tableStyle={{ minWidth: '50rem' }}>
<Column field="name" header="Name" expander></Column>
<Column field="size" header="Size"></Column>
<Column field="type" header="Type"></Column>
</TreeTable>
TreeTable provides onSelect and onUnselect events to listen selection events.
Name | Size | Type |
|---|
<TreeTable value={nodes} selectionMode="single" selectionKeys={selectedNodeKey}
onSelectionChange={(e) => setSelectedNodeKey(e.value)} metaKeySelection={false}
onSelect={onSelect} onUnselect={onUnselect} tableStyle={{ minWidth: '50rem' }}>
<Column field="name" header="Name" expander></Column>
<Column field="size" header="Size"></Column>
<Column field="type" header="Type"></Column>
</TreeTable>
Columns can be grouped within a Row component and groups can be displayed at header and footer using headerColumnGroup, footerColumnGroup properties. Number of cells and rows to span are defined with the colSpan and rowSpan properties of a Column.
Brand | Sale Rate | |||
|---|---|---|---|---|
Sales | Profits | |||
Last Year | This Year | Last Year | This Year | |
| Totals: | $506,202 | $531,020 | ||
| Bliss | 51% | 40% | $54,406.00 | $43,342 |
| Fate | 83% | 96% | $423,132 | $312,122 |
| Ruby | 38% | 5% | $12,321 | $8,500 |
| Sky | 49% | 22% | $745,232 | $650,323 |
| Comfort | 17% | 79% | $643,242 | 500,332 |
| Merit | 52% | 65% | $421,132 | $150,005 |
| Violet | 82% | 12% | $131,211 | $100,214 |
| Dulce | 44% | 45% | $66,442 | $53,322 |
| Solace | 90% | 56% | $765,442 | $296,232 |
| Essence | 75% | 54% | $21,212 | $12,533 |
<TreeTable value={nodes} headerColumnGroup={headerGroup} footerColumnGroup={footerGroup} tableStyle={{ minWidth: '50rem' }}>
<Column field="brand" expander />
<Column field="lastYearSale" />
<Column field="thisYearSale" />
<Column field="lastYearProfit" />
<Column field="thisYearProfit" />
</TreeTable>
Lazy mode is handy to deal with large datasets, instead of loading the entire data, small chunks of data is loaded by invoking corresponding callbacks everytime paging, sorting and filtering occurs. Sample below imitates lazy loading data from a remote datasource using an in-memory list and timeouts to mimic network connection.
Enabling the lazy property and assigning the logical number of rows to totalRecords by doing a projection query are the key elements of the implementation so that paginator displays the UI assuming there are actually records of totalRecords size although in reality they are not present on page, only the records that are displayed on the current page exist.
In addition, only the root elements should be loaded, children can be loaded on demand using onExpand callback.
Name | Size | Type |
|---|
<TreeTable value={nodes} lazy paginator totalRecords={totalRecords}
first={first} rows={rows} onPage={onPage} onExpand={onExpand} loading={loading} tableStyle={{ minWidth: '50rem' }}>
<Column field="name" header="Name" expander></Column>
<Column field="size" header="Size"></Column>
<Column field="type" header="Type"></Column>
</TreeTable>
Incell editing is enabled by defining input elements with editor property of a Column.
Name | Size | Type |
|---|
<TreeTable value={nodes} tableStyle={{ minWidth: '50rem' }}>
<Column field="name" header="Name" expander style={{ height: '3.5rem' }}></Column>
<Column field="size" header="Size" editor={sizeEditor} cellEditValidator={requiredValidator} style={{ height: '3.5rem' }}></Column>
<Column field="type" header="Type" editor={typeEditor} style={{ height: '3.5rem' }}></Column>
</TreeTable>
Adding scrollable property along with a scrollHeight for the data viewport enables vertical scrolling with fixed headers.
Name | Size | Type |
|---|
<TreeTable value={nodes} scrollable scrollHeight="200px">
<Column field="name" header="Name" expander></Column>
<Column field="size" header="Size"></Column>
<Column field="type" header="Type"></Column>
</TreeTable>
Horizontal scrolling is enabled when the total width of columns exceeds table width.
Name | Size | Type 2 | Size 2 | Type 3 | Size 3 |
|---|
<TreeTable value={nodes} scrollable scrollHeight="200px">
<Column field="name" header="Name" expander style={{ width: '250px' }}></Column>
<Column field="size" header="Size" style={{ width: '250px' }}></Column>
<Column field="type" header="Type 2" style={{ width: '250px' }}></Column>
<Column field="size" header="Size 2" style={{ width: '250px' }}></Column>
<Column field="type" header="Type 3" style={{ width: '250px' }}></Column>
<Column field="size" header="Size 3" style={{ width: '250px' }}></Column>
</TreeTable>
A column can be fixed during horizontal scrolling by enabling the frozen property on a Column. The location is defined with the alignFrozen that can be left or right.
Name |
|---|
Size | Type | Size | Type | Size | Type |
|---|
<TreeTable value={nodes} scrollable frozenWidth="200px" scrollHeight="250px">
<Column field="name" header="Name" expander frozen style={{ width: '250px', height: '57px' }}></Column>
<Column field="size" header="Size" style={{ width: '250px', height: '57px' }} columnKey="size_0"></Column>
<Column field="type" header="Type" style={{ width: '250px', height: '57px' }} columnKey="type_0"></Column>
<Column field="size" header="Size" style={{ width: '250px', height: '57px' }} columnKey="size_1"></Column>
<Column field="type" header="Type" style={{ width: '250px', height: '57px' }} columnKey="type_1"></Column>
<Column field="size" header="Size" style={{ width: '250px', height: '57px' }} columnKey="size_2"></Column>
<Column field="type" header="Type" style={{ width: '250px', height: '57px' }} columnKey="type_2"></Column>
</TreeTable>
Columns can be resized with drag and drop when resizableColumns is enabled. Default resize mode is fitthat does not change the overall table width.
Name | Size | Type |
|---|
<TreeTable value={nodes} resizableColumns showGridlines tableStyle={{ minWidth: '50rem' }}>
<Column field="name" header="Name" expander></Column>
<Column field="size" header="Size"></Column>
<Column field="type" header="Type"></Column>
</TreeTable>
Setting columnResizeMode as expand changes the table width as well.
Name | Size | Type |
|---|
<TreeTable value={nodes} resizableColumns showGridlines columnResizeMode="expand" tableStyle={{ minWidth: '50rem' }}>
<Column field="name" header="Name" expander></Column>
<Column field="size" header="Size"></Column>
<Column field="type" header="Type"></Column>
</TreeTable>
Order of the columns can be changed using drag and drop when reorderableColumns is present.
Name | Size | Type |
|---|
<TreeTable value={nodes} reorderableColumns tableStyle={{ minWidth: '50rem' }}>
<Column field="name" header="Name" expander></Column>
<Column field="size" header="Size"></Column>
<Column field="type" header="Type"></Column>
</TreeTable>
Column visibility based on a condition can be implemented with dynamic columns, in this sample a MultiSelect is used to manage the visible columns.
Name | Size | Type |
|---|
<TreeTable value={nodes} header={header} tableStyle={{ minWidth: '50rem' }}>
<Column key="name" field="name" header="Name" expander />
{visibleColumns.map((col) => (
<Column key={col.field} field={col.field} header={col.header} />
))}
</TreeTable>
Particular rows and cells can be styled based on conditions. The rowClassName receives a row data as a parameter to return a style class for a row whereas cells are customized using the body template.
Name | Size | Type |
|---|
<TreeTable value={nodes} rowClassName={rowClassName} tableStyle={{ minWidth: '50rem' }}>
<Column field="name" header="Name" expander></Column>
<Column field="size" header="Size" body={sizeTemplate}></Column>
<Column field="type" header="Type"></Column>
</TreeTable>
TreeTable has exclusive integration with ContextMenu using the onContextMenu event to open a menu on right click alont withcontextMenuSelection and onContextMenuSelectionChange properties to control the selection via the menu.
Name | Size | Type |
|---|
<ContextMenu model={menu} ref={cm} onHide={() => setSelectedNodeKey(null)} />
<TreeTable value={nodes} expandedKeys={expandedKeys} onToggle={(e) => setExpandedKeys(e.value)} contextMenuSelectionKey={selectedNodeKey}
onContextMenuSelectionChange={(event) => setSelectedNodeKey(event.value)} onContextMenu={(event) => cm.current.show(event.originalEvent)} tableStyle={{ minWidth: '50rem' }}>
<Column field="name" header="Name" expander></Column>
<Column field="size" header="Size"></Column>
<Column field="type" header="Type"></Column>
</TreeTable>
TreeTable uses a treegrid element whose attributes can be extended with the tableProps option. This property allows passing aria roles and attributes like aria-label and aria-describedby to define the table for readers. Default role of the table is table. Header, body and footer elements use rowgroup, rows use row role, header cells have columnheader and body cells use cell roles. Sortable headers utilizer aria-sort attribute either set to "ascending" or "descending".
Row elements manage aria-expanded for state along with aria-posinset, aria-setsize and aria-level attribute to define the hierachy.
When selection is enabled, aria-selected is set to true on a row. In checkbox mode, the built-in checkbox component use checkbox role with aria-checked state attribute.
Editable cells use custom templating so you need to manage aria roles and attributes manually if required.
Paginator is a standalone component used inside the TreeTable, refer to the paginator for more information about the accessibility features.
| Key | Function |
|---|---|
| tab | Moves through the headers. |
| enter | Sorts the column. |
| space | Sorts the column. |
| Key | Function |
|---|---|
| tab | Moves focus to the first selected node when focus enters the component, if there is none then first element receives the focus. If focus is already inside the component, moves focus to the next focusable element in the page tab sequence. |
| shift + tab | Moves focus to the last selected node when focus enters the component, if there is none then first element receives the focus. If focus is already inside the component, moves focus to the previous focusable element in the page tab sequence. |
| enter | Selects the focused treenode. |
| space | Selects the focused treenode. |
| down arrow | Moves focus to the next treenode. |
| up arrow | Moves focus to the previous treenode. |
| right arrow | If node is closed, opens the node otherwise moves focus to the first child node. |
| left arrow | If node is open, closes the node otherwise moves focus to the parent node. |