columns.materialize

Whether the columnAggregator result is written into the queried table, which makes the column sortable, filterable and exportable like a regular data column. The cells stay read-only.

It costs a pass over every row on each query, instead of resolving only the rendered cells, and it turns a cell edit into a requery. It requires a local data provider: sorting and filtering of a remote provider run on the server, which does not know the column.

Materialization runs before sorting and filtering, so the aggregator callback receives source table row indexes, and rowId only when data.idColumn is set. Under TreeView or row grouping the column behaves like any other data column: add rowAggregator to it for parent rows to aggregate it.