Filter a report
Two kinds of filter, sharing one shape: a field, an operator, and a value.
Report filters
Click Filters in the toolbar. These apply to every block on the page.
They are authored in the designer and saved with the report — and in view mode
they are live, so a reader can slice the report without editing it. Nothing a
reader changes is written back.
Block filters
Select a block and open Data → Filters. These belong to that block, are
saved with it, and apply in view mode too. A block therefore sees its own
filters and the report's.
Operators
is, is not, contains, starts with, ends with, >, ≥, <, ≤,
between, is one of, is empty, is not empty.
between takes two values, is one of a comma-separated list. is empty
and is not empty need no value at all.
Applying
Values apply on Enter, on leaving the field, or via Apply — not as you
type. A half-typed value would otherwise filter the report to nothing on the
way to a real one, and each keystroke would re-query every block.
How they run
- SQL datasources — the filter is pushed into the
WHEREclause, so the
database does the work rather than the browser discarding rows. - REST, file and Power BI datasources — applied row by row before
aggregation, so a filtered row never reaches aSUM. This is also what makes
tables and KPI cards filter, not just charts.
Numbers are compared as numbers and dates as dates. A zero-padded code such as
007 stays text, so it is not quietly matched as 7.
If a block goes empty
A block showing nothing usually has nothing matching the filters, rather than
being broken. The filter bar says so, and Clear all removes them in one
step.
What filters are not
They do not change what the report is about — the fields a block maps are set
in Data → Mapping. Filter to narrow the rows; remap to change the
question.