Structure guide

Keyed Headers data grid documentation

Keyed headers add a spreadsheet-style coordinate layer to the grid: letters across columns and numbers down rows. Use them when people need to point to cells as B4 or D12 instead of only naming the business column. Turn on annotation when you want to keep the coordinate and the original header visible together.

What it means

Keyed headers add a lightweight coordinate layer on top of the normal labels, so users can point to cells as A1, B4, or C12 without losing the real business headers.

When to use it

Use them for spreadsheet migration, support scripts, QA steps, and training material where people naturally say things like A3 or B12. They also help on dense operational screens when a short coordinate is easier to share in chat, tickets, or walkthroughs than a long field name. Skip them on dashboards and simple reports where business labels already do the job and extra coordinates would add noise.

Implementation notes

Keyed headers work best with selection, clipboard, editing, validation, and formula-driven screens where users already think cell by cell. Column keys are usually the first thing spreadsheet users expect. Row keys matter more when visible row order is part of the workflow too. Keep the normal business headers strong. The coordinate layer should help orientation, not replace meaningful labels.

Relevant API

Start with keyedHeaders.enabled, keyedHeaders.columns, keyedHeaders.rows. Open the live API reference for types and defaults.