Filters can be defined as Analysis filters, Sheet filters or Component filters. If a query is sent to Celonis, all active filters are propagated to the requested table(s). Multiple filters on a table are merged together by a logical AND.
Filter propagation is necessary if there are one or more tables on which a filter is applied, which are not the same as the result table. In that case Celonis propagates the filters to the result table, along the specified join graph. For more information on the join graph see Joins).
All filters in Celonis are stable. Stable in this context means that filters don't interfere with each other. As a result of this, the order of the filters doesn't matter. For example:
returns the same as
Filter stability is also the reason why Celonis doesn't support filters on aggregations, because they would not be stable. For example:
can return a different result than
Comparison against NULL
Applying a filter which compares a column against null or not null always returns an empty result. To filter on all not null values use the ISNULL function. Null represents an unknown value. Celonis can not be sure if two unknown values are not the same.
If a regular filter is set as a sheet or component filter, the affected Dropdown and Button Dropdown components still show all available values. If only those values which respect the filter should be displayed and selectable, a forced filter can be used. Analysis filters are forced by default.
Dropdown component using this regular sheet or component filter:
All values are available in the dropdown menu. Values which do not match the filter condition are displayed in gray color.
Dropdown component using this forced sheet or component filter:
Only values which match the filter condition are available.