What it means
Master / detail keeps the main row list concise while giving users a way to open a richer record view in context.
Data Models guide
Master Detail data grid documentation
Master / detail is for expandable record views. This page covers the client-side setup: master-row rules, expansion ownership, detail height, and toggle-column rendering.
When to use it
Use it when the row list is still the main view and the extra details are secondary or occasional. It is a good fit for work queues, approvals, or investigation flows where users sometimes need deeper context without leaving the table.
Implementation notes
Keep detail panels for supporting context, not information users always need to understand the row. Set a predictable detail height so the expanded state feels intentional and not jumpy. Use the separate SSRM Master Detail page when the main row list is server-backed and you also need `masterDetail.enableServerRowModel`.
Relevant API
Start with masterDetail.enabled, masterDetail.enableServerRowModel, masterDetail.initialExpandedRowIds, masterDetail.expandedRowIds, masterDetail.onExpandedRowIdsChange, masterDetail.isRowMaster, masterDetail.detailRowHeight, masterDetail.renderDetail. Open the live API reference for types and defaults.