Solved: Mutually exclusive issue with QV12 - Qlik Community

sasiparupudi1 · ‎2018-05-03

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‌

sasiparupudi1 · ‎2018-05-18

Hi All,

I have got an update from the qlik support(please see below)

According to our bug tracking system, bug QV-14210 has been fixed. A similar issue with associative selection has been reported before in bug QV-14178, and the fix applies for both bugs. The bug fix will be delivered in the next version of Qlik Engine. We have no further information of which release will contain this fix or specific release schedule. However, as the fix has been deployed to Qlik Engine, the release should come in the near future.

Thanks you all for your help and helpful advise/comments in this.

View solution in original post

Miguel_Angel_Baeyens · ‎2018-05-03

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

Peter_Cammaert · ‎2018-05-03

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...

Peter_Cammaert · ‎2018-05-03

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

olivierrobin · ‎2018-05-03

hello

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

Peter_Cammaert · ‎2018-05-03

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?

sasiparupudi1 · ‎2018-05-04

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

sasiparupudi1 · ‎2018-05-07

Hi

Any more comments on this please?

hic‌

mto‌

Rob Wunderlich

Miguel_Angel_Baeyens · ‎2018-05-07

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.

sunny_talwar · ‎2018-05-07

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