rows.forEachExcept fell back to the filtered rows: this source cannot exclude one column's filter, so the result is narrowed by the column you asked to leave out.

Warnings reference › rows.forEachExcept.unsupported

Identifier

rows.forEachExcept.unsupported

Raised by

The grid (core)

Since

1.12.0

What happened

forEachExcept exists so that a facet or cross-filter panel can show the counts that would apply if its own filter were lifted. A source that fetches on demand cannot answer that question, so the walk falls back to the ordinary filtered rows - which *are* narrowed by the very column you asked to exclude. A cross-filtering panel on that fallback collapses to the single value the user just clicked, which is exactly the failure the exclusion prevents.

The fix

Cross-filtering needs a memory source. On a remote or paged source, exclude the column's filter in your own query instead.

Reference

Covered in full at the API reference.