Qlik Sense Measure values display incorrectly, showing null value instead of the expected data

Nao_Baba — Tue, 21 Oct 2025 07:17:12 GMT

The measure value is suddenly not displayed correctly, but it started to show null value instead. It used to show a proper data until Nov 2024 release or earlier.

The issue is observed when:

Measures have no aggregation function (such as SUM(), COUNT())
Fields include only one data and null value

Environment

Qlik Cloud (at documentation)
Qlik Sense Enterprise on Windows May 2025 and November 2025

Resolution

QCB-33031 will be fixed in Qlik Cloud at the first opportunity. Qlik Sense Enterprise on Windows will have the fix introduced in the next major release in 2026.

Workaround One

Apply aggregation or Only() function to the affected measure.

Workaround Two

For Qlik Sense Enterprise on Windows, add the parameter UseTableEvaluatorWhenApplicable=0 to the Qlik Sense engine settings.ini file. The change must be done on all engines, if more than one is in use.

The setting indicates engine to use the old way to calculate the measures without aggregation. It is slower, but the behavior remains what it was back in Qlik Sense November 2024 and earlier.

See How to modify Qlik Sense Engine's Settings.ini for reference.

Cause

The difference in behavior is due to an internal change in the Qlik Sense Engine introduced to improve performance.

Previously, when a measure was defined directly as a field without an aggregation, the Engine automatically applied the Only() function. This function returns a value if the field contains only a single distinct (non-null) value.

See The importance of Only().

However, appending Only() function leads to slow performance. To optimize performance, the Engine now uses a more efficient calculation method. As a side effect, when a field contains one valid value and one null value, the result is returned as null instead of the expected value.

This issue has been identified as QCB-33031, and will be fixed to display the proper value instead of null in this scenario.

Internal Investigation ID(s)

QCB-33031