the "{label}" tile cannot be computed over a...

Warnings reference › kpi:pivot-unsupported:*

Identifier

kpi:pivot-unsupported:*

Raised by

KPI

Since

1.79.0

What happened

A pivot's terminal groups are pushed down and answered as aggregated cells: they carry no leaf rows at all, so grid.rows.leavesOf answers empty under one. A sum/avg/min/max tile over a plain column with no filter still computes through the engine's grand-total query (kpi:engine-page:* covers that path failing); this warning is for every tile that has no such fallback at all - a count, a countDistinct, a custom reduction, or a filter function only the browser can run. The tile reports unknown with a null value rather than a confident zero read over nothing.

The fix

There is no fix that keeps the same tile kind over a pivoted grid: switch the tile to a sum/avg/min/max over a plain column with no filter (routed through the engine), or read the number from the grid's own pivot cells instead of a KPI tile.

Reference

Covered in full at the API reference.