Applies to:  CELONIS 4.0 CELONIS 4.2 CELONIS 4.3 CELONIS 4.4 CELONIS 4.5 CELONIS 4.6 

Description

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

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).

Stable Filter

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:

FILTER table.col > 400; FILTER table.col < 600;

returns the same as

FILTER table.col < 600; FILTER table.col > 400;

Filter stability is also the reason why Celonis doesn't support filters on aggregations, because they would not be stable. For example: 

FILTER table.col > 400; FILTER AVG(table.col) < 400;

can return a different result than

FILTER AVG(table.col) < 400; FILTER table.col > 400;

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.

Syntax

FILTER [FORCED] condition;

Forced Filter

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.

Example

Dropdown component using this regular sheet or component filter:

FILTER "Table"."Country" IN ('DE','US');

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:

FILTER FORCED "Table"."Country" IN ('DE','US');

Only values which match the filter condition are available.

Examples


[1] Example where one filter is applied to the query. The filter condition excludes the second input row.

Query
Filter
FILTER "Numbers"."number" != 22
Column1
"Numbers"."id"
Column2
"Numbers"."number"
Input
Numbers
id : INTnumber : INT
1
13
2
22
3
34
Output
Result
Column1 : INTColumn2 : INT
1
13
3
34



[2] Example where one filter is applied to the query. The filter condition excludes the second input row.

Query
Filter
FILTER "Numbers"."number" IN (13, 34)
Column1
"Numbers"."id"
Column2
"Numbers"."number"
Input
Numbers
id : INTnumber : INT
1
13
2
22
3
34
Output
Result
Column1 : INTColumn2 : INT
1
13
3
34



[3] Example where two filters are applied to the query. Both filter conditions are merged together by a logical AND. The first filter condition excludes the second input row, and the second filter condition excludes the first input row. Therefore, only the third row appears in the result.

Query
Filter
FILTER "Numbers"."number" IN (13, 34)
Filter
FILTER "Numbers"."id" IN (2, 3)
Column1
"Numbers"."id"
Column2
"Numbers"."number"
Input
Numbers
id : INTnumber : INT
1
13
2
22
3
34
Output
Result
Column1 : INTColumn2 : INT
3
34



[4] Example where one filter is applied to the query. The SUM aggregate function is applied after the filter has been applied to the input table.

Query
Filter
FILTER "Numbers"."number" IN (13, 34)
Column1
SUM("Numbers"."number")
Input
Numbers
id : INTnumber : INT
1
13
2
22
3
34
Output
Result
Column1 : INT
47



[5] Example where two filters are applied to the query. Both filter conditions are merged together by a logical AND. The first filter condition excludes the first and third input row, and the second filter condition excludes the second and third input row. Therefore, the result is empty.

Query
Filter
FILTER "Numbers"."number" NOT IN (13, 34)
Filter
FILTER "Numbers"."id" = 1
Column1
"Numbers"."id"
Column2
"Numbers"."number"
Input
Numbers
id : INTnumber : INT
1
13
2
22
3
34
Output
Result
Column1 : INTColumn2 : INT



[6] Example of two joined tables where one filter is applied to the query. The filter condition excludes the last row of the companyDetail input table, therefore, the last two rows of the caseTable are excluded.

Query
Filter
FILTER "companyDetail"."country" = 'DE'
Column1
"caseTable"."caseId"
Input
caseTable
caseId : INTcompanyCode : STRINGvalue : INT
1
'001'
600
2
'001'
400
3
'001'
200
4
'002'
300
5
'003'
300
6
'003'
200
companyDetail
companyCode : STRINGcountry : STRING
'001''DE'
'002''DE'
'003''US'

Foreign Keys
caseTable.companyCodecompanyDetail.companyCode
Output
Result
Column1 : INT
1
2
3
4



[7] Example of two joined tables where one filter is applied to the query. The filter condition excludes the last four rows of the caseTable.

Query
Filter
FILTER "caseTable"."value" > 300
Column1
"caseTable"."caseId"
Column2
"companyDetail"."country"
Input
caseTable
caseId : INTcompanyCode : STRINGvalue : INT
1
'001'
600
2
'001'
400
3
'001'
200
4
'002'
300
5
'003'
300
6
'003'
200
companyDetail
companyCode : STRINGcountry : STRING
'001''DE'
'002''DE'
'003''US'

Foreign Keys
caseTable.companyCodecompanyDetail.companyCode
Output
Result
Column1 : INTColumn2 : STRING
1
'DE'
2
'DE'



[8] Applying a filter which compares a column against null always returns an empty result.

Query
Filter
FILTER Table1.Column1 = null
Column1
Table1.Column1
Input
Table1
Column1 : INT
1
null
Output
Result
Column1 : INT



[9] Applying a filter which compares a column against not null always returns an empty result.

Query
Filter
FILTER Table1.Column1 != null
Column1
Table1.Column1
Input
Table1
Column1 : INT
1
null
Output
Result
Column1 : INT


  • No labels