filters.where ({names}) runs over the rows the {mode} source fetched, not the whole dataset: match counts and totals are page-relative. Give the predicate a { condition } twin so the engine can narrow the fetch itself.

Warnings reference › source.where.pageRelative

Identifier

source.where.pageRelative

Raised by

The grid (core)

Since

1.56.0

What happened

The predicate does run - over the window this source has fetched. Every row on screen is judged, and the counts and totals describe that window rather than the dataset, so a figure read off the grid is page-relative.

The fix

Register the predicate with a { condition } twin: the grid pushes the condition to the source so the narrowing happens where the whole set is, and runs your function locally as the authority.

The smallest fix

grid.filters.where('mine', fn, { condition: { colId: 'owner', op: 'eq', value: me } });

Reference

Covered in full at the API reference.