Locked Fields Dropping After QVW Reload

[#1]

We just upgraded to QV11 IR1, and we are experiencing problems with locked fields dropping after the QVW is reloaded.  Is anyone else having this problem?

Thanks. - Mike

[#2]

Clarification... Locked fields are dropping their selected value after the reload.  After the reload, no value is selected for that field that was locked.  The field remains locked though, even though there is no selection.

[johnw]

I'm using QlikView 10, but I've sometimes seen something that may be similar.  Sometimes we have problems with loading the data, and the default value we had in a "Always One Selected Value" field no longer exists, so the "Always One Selected Value" checkmark disappears.

Our solution has been to always configure these default selections with macros or actions and NOT rely on any direct configuration saved with the document.  Even if I can't explain why QlikView would be dropping your field value but keeping the lock, I suspect that having an OnOpen trigger for an action that sets and locks the value would work around the problem.

[#4]

You use the attached QVW you can replicate the bug. 

I am working with a support rep to see if I can get a fix for this.  I am using QV version 11.00.11282.0 SR1 64 bit edition. 

Here are the steps to reproduce the bug:

In the QVW, press the button “Lock IL1 to ‘abcde’ value”. 

You will see that ‘abcde’ value is selected IL1 field and locked with a grey color.

Reload the application.

Then you will see that the lock was removed, an all values are showing again.

But, if you run the same test, and just manually click on the ‘abcde’ value, and then right click to lock the value, then reload, you will see that that value remains selected, and locked.

So it looks like reloading doesn’t retain locked field values, when the lock and select occurs via a macro.

[#5]

Has anyone else ran into this bug?

[johnw]

Both ways work the same and maintain the locked value for me in version 10.00.9282.8 (64 bit), so it looks like a recent bug.  What about doing it with actions instead of a macro?

[#7]

I have just experienced this same bug in version 11.0.11426.0 SR2 64-bit.

To clarify, I had a locked year field.  When reloading the document, the selection dropped and I was no longer able to select a year.  I had to click the unlock button for functionality to return.

@plantm - Have you had any luck with QV support?

[#8]

Not yet. They said to use the built in Actions instead of Macros, but I am experiencing the same problem with Actions as well.

[fosuzuki]

Same error for me in v11.0.11440 (SR2 Update 2).

[#10]

I have also experienced this bug using QV 11 SR2.  This bug also seems to occur if a static report is printed.