Data Models guide

Tree Data data grid documentation

Tree data is for record-owned hierarchies such as folders, org charts, or nested projects. This page shows where the path comes from, how the tree renders it, and how that differs from Row Grouping.

What it means

Tree data is for records that already belong to a hierarchy, such as folders, org charts, or nested projects.

When to use it

Use it when each row already has a stable parent-child route in the business model. Prefer row grouping when users should be able to create groups from otherwise flat rows during the session.

Implementation notes

Tree Data reads a route from the records; Row Grouping creates UI groups from flat rows. Choose a clear group column so users always know which visible cell is carrying the tree structure.

Relevant API

Start with treeData.enabled, treeData.getDataPath, treeData.pathColumnKeys, treeData.pathField, treeData.pathSeparator, treeData.defaultExpanded, treeData.groupColumnKey. Open the live API reference for types and defaults.