Capabilities Grids

Any table size, one grid: scroll, sort, filter, edit, export.

The grid renders the rows in view and fetches the next window as you scroll; sorting, filtering and aggregation are pushed down to the source or the bed.

golden.material · 48,213,907 rowsviewport: 60 rows renderedscroll · sort · filter · group · exportThe engine does the worksort and filter pushed down to the source or the bedaggregates computed before rows travelnext window fetched as you scroll, keys kept stableedits validated per cell, saved per row, loggedexports run under the same security filters
A window of rows rendered; the engine does the sorting, filtering and aggregation; exports run under the same security.
48.2M
rows in the showcase material table, scrolled from one grid
showcase
60
rows rendered at a time; the rest fetched as you scroll
product
1,284
concurrent users at a 3.1 s p99 on the showcase estate
showcase
0
row limit on governed exports
product
Step by step

What the grid does when you scroll, sort and edit

OpenThe grid asks the engine for the first window with the default sort; the engine pushes the sort and any filter down and returns 60 rows and the total count.
What you see

The material grid on the showcase estate

golden.material · 48,213,907 rows · sorted by stock valuefilters: plant 1210 · activegroup by: nonewindow 4 of 803,565
materialdescriptionplantstockvaluelead timerule
M-1183920resistor 470 Ω 1% 06031210128,400€2,33721 dpass
M-2200417housing, cast, 220 mm12103,180€412,30042 dlead time drift
M-0091114bearing 6204-2RS200018,900€27,40514 dpass
M-3391005controller board rev C1210412€184,21070 dover 12 weeks safety

Columns come from the golden view and from the transactions in the same bed: description and lead time are master data, stock and value are live facts. The rule column shows the latest rule results per row, and a click opens the rule's evidence.

Why it stays fast

The engine does the work

The grid holds only a window of the table. Every sort, filter, group and aggregate is a query the engine pushes to the source or runs on the bed, and only the rows in view travel. Keys stay stable across windows, so an edit on row 3 million lands on the right row after a re-sort.

The same component renders a steward's cluster of fourteen records, a drill-down from a pivot cell into 214,000 order lines, and a governed extract of the whole table; each is one query with the same security.

Window60 rows rendered; the next fetched at 40
Pushdownsort · filter · group · aggregate
Keysstable across windows and re-sorts
Editingcell validation · row save · rule run · survivorship
Exportany size · your identity · logged
How master-data hubs usually do it

What is standard, and what is different here

Hub interfaces page results and cap exports; inline and bulk editing are common; spreadsheet-style editing appears in some products. Virtual scrolling with pushdown is rarer, and where it exists it covers the hub's own tables, because the transactions sit elsewhere.

Here the grid scrolls the federated result set, so a transaction table of tens of millions of rows and a master table of thousands look and behave the same, and an export has no fixed row cap.

Standard everywherepaged results; inline edit; bulk update; capped exports
Herevirtual scrolling over federated results; governed exports of any size
Consequenceone grid for master data, transactions, clusters and drill-downs
Terms on this page

Virtual scrollingRendering only the rows in view and fetching the next window as you scroll.
PushdownSending sorts, filters and aggregates to the source or the bed so only the needed rows travel.
Governed extractAn export run as the person's identity, with masks and row filters applied and the export logged.
Questions

Can I edit transactions in the grid?

Where the domain allows it and the owning system accepts a write-back: a planner edits a forecast row; an order line stays read-only unless the process app owns the change.

How does the grid handle a slow source?

The window request carries a time budget; a source over budget answers from its cached or replicated contract, and the column says so.

Is there a spreadsheet add-in?

The workbench exposes the same grid through SQL to spreadsheets; a native add-in is on the roadmap (see the review notes).

See your first domain built on your data

Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.