the "{label}" tile's {aggregation} cannot be...

Warnings reference › kpi:aggregate-unpushable:*

Identifier

kpi:aggregate-unpushable:*

Raised by

KPI

Since

1.79.0

What happened

A countDistinct tile is bound to a grid on a paged pushdown source that holds fewer rows than match, and the engine could not be asked for it - a filter function, a field that is not a plain column, a source whose aggregates config keeps the statistic in the browser, a filter the engine cannot apply, or a failed request. Unlike sum/avg/min/max, a page's distinct count is not a lower bound or a useful partial reading - the same values can recur on pages that have not loaded, so a bigger page does not converge toward the relation's true count. The tile shows no number and reports the unknown status instead of a figure that looks real and is not, a demo reported 103 destinations for a relation of 354).

The fix

The reason names what stopped the push: route the statistic to the engine (aggregates: { default: 'engine' } on the pushdown source), bind the tile to a plain column, or express the tile's filter as a grid filter the engine can apply.

The smallest fix

tiles: [{ id: 'destinations', label: 'Destinations', aggregation: 'countDistinct', field: 'dest_name' }]

Reference

Covered in full at the API reference.