topic Re: Unexpected behavior with Null in Set Analysis in App Development

Unexpected behavior with Null in Set Analysis

dafnis14 — Mon, 08 Oct 2018 16:47:37 GMT

Hi,

I ran into an unexpected result with a Set Analysis expression:

sum({<Line_Flag_ManualIncome ={1}>} LineTotalFinal)

When the value of Line_Flag_ManualIncome is null, all values are taken into account.

There is a similar thread here:

https://community.qlik.com/message/1390416#1390416

I would also suggest it's a bug, or a very counter-intuitive behavior of Qlik.

I'm aware of the workarounds, but hope that it would be fixed.

Re: Unexpected behavior with Null in Set Analysis

Ivan_Bozov — Mon, 08 Oct 2018 18:27:10 GMT

What release are you using? I experienced this as well in one of the newer releases. The solution would be to assign a value to the empty fields in the script, e.g. by using NullAsValue.

There is also another thread here which describes a similar problem. Read the comment by Henric Cronström, it might give you some insight: https://community.qlikview.com/thread/307415

Re: Unexpected behavior with Null in Set Analysis

dafnis14 — Tue, 09 Oct 2018 05:29:56 GMT

Hi Ivan,

I'm using June release.

I looked at the thread, and it's not similar to what I'm facing.

Instead of ignoring null values, they are taken into account in the set analysis, which is not expected...

Thanks for the NullAsValue tip!

Re: Unexpected behavior with Null in Set Analysis

Ivan_Bozov — Tue, 09 Oct 2018 06:20:16 GMT

Hi, I was mostly referring to the comment of Henric, where he explains the difference between blanks and NULLs and how they are handled by Qlik. Anything else should be a bug.

Anyway, (I believe that since the June release) I also started to experience some issues with set analysis expressions that worked differently before in cases where the field has some NULL values. For me there is no doubt that Qlik changed something but cannot say what exactly they did.