NULL FIELD PROBLEM IN SET ANALYSIS

[caio_caminoski]

Hello community,

I have a metric that uses a set analysis (  {<FIELD ={'Y'}>}  ) . My problem starts when all the values of my 'FIELD' are null. Qlik completely ignores that null is different than 'Y' and don't even bother evaluating the set analysis, giving me the total sum of the value field instead of 0.

For example, in the script:

TABLE:

Load

RowNo() AS CODE

    ,Null() AS DIM

    ,1 AS VALUE

AutoGenerate 15;

In the KPI:

Sum( {< DIM = {'Y'} >} VALUE)

As there is no data 'Y' in the field DIM i should be getting 0, but instead I am getting 15.

Any ideas?

[simonaubert]

Thanks. 

It totally sounds like a bug or at least a very bad user experience. I lost one hour trying to understand why my set analysis is not working and now. 😞

So, we all agree the {'*'} does not work when the field is totally null. Great.  Really great.

[simonaubert]

I posted this idea if you want to vote :
https://community.qlik.com/t5/Qlik-Sense-Enterprise-Ideas/Natural-management-of-completly-null-field...

[jasasri_90]

Hi caio,

Did you find any solution .

Regards,

Jasasri 

[simonaubert]

Hello,

This is a bug knows as QB-726. I made it open in december 2019, we're in October 2020.

Best regards,

Simon

[phreesia_qv3]

Hello, is there any update to this issue? We are running into the same problem