Mutually exclusive issue with QV12

[sasiparupudi1]

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:

1. Open the file
2. Select IsYTD=YTD
3. Select Year=2017

Outcome (mutually exclusive selections stay):

@jtg

tresesco‌

stalwar1‌

[sasiparupudi1]

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

[sunny_talwar]

Can you elaborate on this?

this issue is getting affected by the set analysis

affected by set analysis? how?

[sasiparupudi1]

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

[sunny_talwar]

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.

[Peter_Cammaert]

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.

[sunny_talwar]

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

[Peter_Cammaert]

Probably.

[sasiparupudi1]

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

[Anonymous]

im version 12.10 sr2 ...

doing the steps to replicate the problem

Steps to replicate:

1. Open the file
2. Select IsYTD=YTD
3. 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

[Anonymous]

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