topic Re: Mutually exclusive issue with QV12 in QlikView

Mutually exclusive issue with QV12

sasiparupudi1 — Wed, 25 Nov 2020 16:16:04 GMT

We are facing the following problem when we upgraded our qlikview from 11 to qv12.1 sr 7. Could you please help us find a solution /workaround to this issue?

Steps to replicate:

Open the file
Select IsYTD=YTD
Select Year=2017

Outcome (mutually exclusive selections stay):

@jtg

tresesco‌

stalwar1‌

Re: Mutually exclusive issue with QV12

Miguel_Angel_Baeyens — Thu, 03 May 2018 14:58:29 GMT

I cannot reproduce it, but you should contact Qlik Support to address this as best as possible.

Re: Mutually exclusive issue with QV12

Peter_Cammaert — Thu, 03 May 2018 15:02:59 GMT

This is weird. Selections that don't associate in any way stay selected, but only internally. I needed a Current Selections object to see what was selected, because the listboxes for Year and IsYTD show only not-associated results...

Even in 12.20SR4.

Pretty serious bug in the associative logic, if you ask me...

Re: Mutually exclusive issue with QV12

Peter_Cammaert — Thu, 03 May 2018 15:05:37 GMT

I think you should do as Miguel suggested: contact Qlik Support.

Re: Mutually exclusive issue with QV12

olivierrobin — Thu, 03 May 2018 15:06:17 GMT

hello

if you delete you list box IsYTD, copy IsPYTD and use the copy for IsYTD, everything becomes ok

Re: Mutually exclusive issue with QV12

Peter_Cammaert — Thu, 03 May 2018 15:26:59 GMT

When I open a new QVW document, copy/paste your original script into it and Reload, then everything works as expected (as far as I can see). Maybe your document is slightly corrupt?

Re: Mutually exclusive issue with QV12

sasiparupudi1 — Fri, 04 May 2018 07:41:48 GMT

Yes Peter, this looks like a serious bug, we have logged an issue with qlik and they escalated it to their r&d

Re: Mutually exclusive issue with QV12

sasiparupudi1 — Mon, 07 May 2018 12:34:23 GMT

Any more comments on this please?

hic‌

mto‌

Rob Wunderlich

Re: Mutually exclusive issue with QV12

Miguel_Angel_Baeyens — Mon, 07 May 2018 13:06:09 GMT

I don't see any further comments possible here. If you reported to Qlik Support, that's it. If it can be reproduced by others, it is very likely a bug on the product that they have to fix.

Re: Mutually exclusive issue with QV12

sunny_talwar — Mon, 07 May 2018 14:14:41 GMT

Weird thing is that it doesn't happen if I select IsYTD = YTD and Year = 2016 or Year = 2015. Only time it happens (have not tested all combination, but based on the combinations tested) is when IsYTD = YTD and Year = 2017

Re: Mutually exclusive issue with QV12

sasiparupudi1 — Mon, 07 May 2018 14:20:09 GMT

Yes, sunny, this issue is getting affected by the set analysis

Re: Mutually exclusive issue with QV12

sunny_talwar — Mon, 07 May 2018 14:22:22 GMT

Can you elaborate on this?

this issue is getting affected by the set analysis

affected by set analysis? how?

Re: Mutually exclusive issue with QV12

sasiparupudi1 — Mon, 07 May 2018 15:05:21 GMT

If you delete the text box containing the set analysis expression , save the qvw and re open it, it works normally

Re: Mutually exclusive issue with QV12

sunny_talwar — Mon, 07 May 2018 15:25:27 GMT

Okay, that makes sense.... I am able to replicate the problem now... pcammaert‌ can you try this with the new information provided. I am attaching the file where I tested by copy pasting the script from sasiparupudi1‌'s file.

Re: Mutually exclusive issue with QV12

Peter_Cammaert — Mon, 07 May 2018 15:41:46 GMT

I loooks like it is indeed the Set Analysis expression that causes QlikView to break down. Again also in 12.20SR4

Sunny, I used my own test document that had just the original load script and some listboxes (all freshly created) As Sasidhar said and after doing the reverse test, they all work as expected until you add a text box with the simple set analysis expression:

=count(DISTINCT {<Year={'2017'}>} EffectiveDate )

And now for the annoying part: then I dropped the text box (including all copies of the set analysis expression) and pressed the Clear button a couple of times, but my document stays broken. Saving doesn't help. I really have to clear

-save-close and reopen to get it to work again. If I forget to clear the weird selection situation, my document stays broken forever.

I do hope that Qlik Support assigns a high-enough priority to fixing this.

Re: Mutually exclusive issue with QV12

sunny_talwar — Mon, 07 May 2018 15:52:03 GMT

And now for the annoying part: then I dropped the text box (including all copies of the set analysis expression) and pressed the Clear button a couple of times, but my document stays broken. Saving doesn't help. I really have to clear

-save-close and reopen to get it to work again. If I forget to clear the weird selection situation, my document stays broken forever.

I did not face this issue, something to with Qlik Versions? I am on Version 12.10 SR2

Re: Mutually exclusive issue with QV12

Peter_Cammaert — Mon, 07 May 2018 15:53:54 GMT

Probably.

Re: Mutually exclusive issue with QV12

sasiparupudi1 — Tue, 08 May 2018 06:39:40 GMT

Logged an issue with qlik support.. Let us see what they say

Re: Mutually exclusive issue with QV12

Anonymous — Tue, 08 May 2018 06:51:27 GMT

im version 12.10 sr2 ...

doing the steps to replicate the problem

Steps to replicate:

Open the file
Select IsYTD=YTD
Select Year=2017

was able to replicate and see the document not able to associate ..

but i did reload the document ... it went okay.

i forgot.. i removed the =count(DISTINCT {<Year={'2017'}>} EffectiveDate ) text..

maybe caused to correct

Re: Mutually exclusive issue with QV12

Anonymous — Tue, 08 May 2018 09:39:32 GMT

Hi All

I managed to recreate this on QlikView 12.10 SR7, Qlik View 12.20 SR2, Qlik Sense November 2017 release and Qlik Sense Feb 2018 release. I have not been able to recreate this in any version of QlikView 11

So it seems whenever you have set analysis, the value is being treated as if it is in scope when applying a filter on the identifier. Example: sum({<Year = {2018}>} Sales) - the value '2018' will be selectable on the 'Year' dimension without removing excluded filters. It will only apply to the value '2018' (or any value listed in set analysis).

The only way to 'reset' it, is to remove the set analysis, save and close or reload.

This happens even when the set analysis is only declared in a variable (and not used in the dashboard).

EDIT: I don't believe this is a bug - seems to be the way the engine works considering all the versions tested.

Sample Attached