the {adapter} adapter was not asked to group this query because {reason}. The engine returns rows and the grouping is the grid's to do, which needs every matching row in the browser - correct where the grid holds them, and wrong-looking where it holds a window. `lastPlan().unpushed` names it.

Warnings reference › source.pushdown.group.*.*

Identifier

source.pushdown.group.*.*

Raised by

The grid (core)

Since

1.63.0

What happened

Grouping was not pushed for the reason named. The grid groups what it holds: right when it holds every matching row, and visibly wrong - group counts and subtotals describing a page - when it holds only a window.

The fix

The reason is printed in the message and is also in lastPlan().unpushed. Widen the adapter, or arrange for the grid to hold the whole set.

Reference

Covered in full at the API reference.