Show parent and child records as one grid people can expand, read and act on. Open it from any account and it climbs to the top of the hierarchy. Configure it once, then place it in a Screen Flow, on a Lightning page or on an Experience site.
A flat table repeats the parent on every row. A tree grid shows it once, with its children under it. Four things people do with it, each filmed in a real Salesforce org, each turned on with a property.
Currency, percent, badges, progress bars and avatars: the Data Table's 30+ column types, on parents and children alike.
An account, its opportunities, then the contacts on each deal. Each level comes from its own object and its own query.
Each row carries its actions, such as logging a call or opening a flow. Column headers carry their own, wired to an interaction the same way the Data Table does it.
The Tree Grid ships in three Avonni component sets, with the same columns, the same actions and the same behaviour. In your own code, LWC Components gives you the Tree.
<avonni-dd-tree
query={accountsQuery}
mapping={accountMapping}
show-item-count>
</avonni-dd-tree>Every item below is in the current release, on the packages named.
Give the grid a parent lookup and the current record Id. It climbs to the top of that branch, draws the whole tree and marks the row you came from.
Columns carry their own header actions, each wired to a Column Header Action Click interaction.
A Tree Grid can open with every level showing, for the short trees people read in one glance.
The Tree Grid reached the Component Builder and Experience Builder, with the Data Table's column types, sorting, row selection and load more.
The Tree Grid arrived in Flow Screen Components, building the hierarchy from a query.
Users ask, we ship.
See every shipped ideaReal screens built with Avonni, one industry job each. Open one to see it run and copy its code, or try the Tree Grid on its own and change any property live.
Salesforce's View Account Hierarchy opens the tree on a page of its own. The Tree Grid puts the same tree on the record, in a flow or on a portal, with your columns and your actions. Two things it does not do yet: search inside the grid, and an expand all button for users. You can open it fully expanded instead, best kept for trees of a few hundred rows.
Browse the component librarySee where another component runs, and how it is configured.
Install the package, point the Tree Grid at an account and see the whole hierarchy in your own org before the day is out.