filters.where("{name}") is registered but the {mode} source holds only its fetched window and cannot run the predicate over it: the predicate is not applied there, and rows it would exclude stay on screen. Give it a { condition } twin so the engine can narrow the fetch itself - that is the supported route for a paged or remote source.

Warnings reference › source.where.notApplied:*

Identifier

source.where.notApplied:*

Raised by

The grid (core)

Since

1.56.0

What happened

Stronger than the page-relative case: this source cannot run the predicate at all, so it is not applied and the rows it would have excluded are visible. The grid is showing more than the predicate says it should.

The fix

Give the predicate a { condition } twin so the narrowing is done by the engine.

Reference

Covered in full at the API reference.