topic "Always One Selected Value" conflict might cause unknown outcomes in QlikView

"Always One Selected Value" conflict might cause unknown outcomes

thomas_wang — Sat, 16 Nov 2024 04:28:09 GMT

Hi Community,

This time I want to throw out this question which I though is as serious as "Null values in Nested Syn Keys". I hope as many people as last time have a discussion with me, though community constraints may be greater than ever.

Here still is a very simple example.

AB:
LOAD * Inline [
A, B
a1, b1
a2, b2
];

AC:
LOAD * Inline [
A, C
a1, c1
a2, c2
];

Do this load, and then set all fields A, B, C with "Always One Selected Value".

Next, back to scripts, edit as below.

AB:
LOAD * Inline [
A, B
a1, b1
a2, b2
];

AC:
LOAD * Inline [
A, C
a2, c2
];

Please notice that "a1, c1" has been remove from table "AC". Then do the reload...

Maybe we can't predict what will happen next. If you are lucky enough, you may not get an error message and the program still seems to be running correctly. Then please save it as another QVW and open the new one again. I think you'll be surprised, because you didn't modify any front-end design, you just reloaded the script.

BTW, I still use 11.20.12235.0 SR5 64-bit Edition. I'm not sure you'll get the same result if you use version 12.

Re: "Always One Selected Value" conflict might cause unknown outcomes

thomas_wang — Wed, 13 Feb 2019 08:27:10 GMT

In practice, due to the diversity of situations, when such conflicts occur, we will get a variety of results, including but not limited to weird front-end display, service death, report can not be opened and with a variety of weird error hints.

Re: "Always One Selected Value" conflict might cause unknown outcomes

olivierrobin — Wed, 13 Feb 2019 10:28:19 GMT

hello

yesterday, I posted this :

https://community.qlik.com/t5/QlikView-App-Development/strange-behavior-of-quot-always-one-selected-value-quot/td-p/1543117

which seems to be another strange behavior of this option

I tested your case in 12.10 and it's very strange