pplCRM

Filters and the query builder

From one-click tag filters to full and/or queries, and how active filters always stay visible as removable chips.

1 min read

Filters narrow a grid to the rows you care about, and pplCRM never hides what it is doing: a small funnel marks the filter row above the grid, every active filter appears as a chip there with a count of how many rows match, and dashed entry pills sit inline. Remove one chip, or Clear all at once.

Quick filters: the dashed pills

  • + Add filter: pick a field, an operator, and a value; the condition lands as one removable chip.
  • Tags: check one or more tags; checked tags combine with OR (match any) and land as a single removable chip.
  • Issues: same mechanics as tags, for issue interests.
  • Lists: show only the members of one list.

Per-column filters

Advanced Filters opens a filter row under the column headers: type a condition per column (a name fragment here, a city there), and the grid narrows to rows matching all of them.

The query builder

When per-column matching is not expressive enough, the Advanced Query Builder composes full conditions with and/or groups: “city is Springfield AND (donated this year OR volunteers)”. It is the same builder that powers dynamic lists, so a query you like can become a list that maintains itself.

Why is one of the filter buttons disabled?
Per-column filters and the query builder are mutually exclusive. Mixing both would make the result impossible to reason about. Clear one to use the other.
Filters follow you into records
Open a record from a filtered grid and the pager reads “N of M filtered”. J/K walk exactly the set you filtered, in order.
Related

Try this on sample data.

Every feature in the docs is live in the free demo workspace — no card, nothing to lose.

Start free