Qlik Sense May 2021, QlikView 12.60 : Count expression returned a distinct count instead of the expected non-distinct count.

[Christopher_prem]

Non-distinct Count expression Count(Num) returns a distinct count, instead of the expected non-distinct count.

Environment:

Qlik Sense Enterprise on Windows May 2021 and later
Qlik Sense Business 
Qlik Cloud 

#QlikView 12.60 and later

This change in behaviour follows the bug fix QB-3895.

Ensure deterministic table order traverse for key fields.

This eliminates the problem with aggregations containing references to key fields, being dependent on the declaration order of the tables in the script. In addition, an aggregation over a key field that resides in more than two tables will always be forced to show a distinct result.

The strict new table traverse order for key fields may affect legacy calculations that contain an aggregation over a key field. Calculations that previously did return a distinct (by chance) result, will return a non-distinct result instead.

The fix is delivered with the opt-out flag SortKeyFieldTables (default value 1).

 

Resolution:

Set SortKeyFieldTables  to 0 in Settings.ini under "Settings 7" for legacy bahaviour:

SortKeyFieldTables=0

This change in behavior is intentional (as designed) and was documented in a release note. Affected calculations will have to be complemented with the distinct prefix in the relevant aggregation where the distinct calculation is the intended result.