topic Cannot Select Items in a List Box in QlikView

Cannot Select Items in a List Box

Tue, 03 Mar 2015 13:56:10 GMT

One list box in a dashboard suddenly stopped working properly in our web client. All linked list boxes for the same dimension are affected (3). These linked list boxes are on different sheets. Items in the list box are white, indicating they are selectable, however, when users click on them they momentarily turn green then go back to white without selecting the item(s). We have many production dashboards, but only this one dashboard and this single dimension in it seem affected.

The dashboard uses section access, but this phenomenon still occurs when section access code in the dashboard script is disabled. There are no alternate states. There are no triggers associated with the list box or dimension in question.

Both the QA and Production versions in the web client are affected. This problem does not occur in QV desktop for either the QA or Dev versions, making it very difficult to diagnose. In the past, we have seen some similar and unusual behavior from this dashboard, but it would vanish when the dashboard was published the next day. This time, the problem persists.

Has anyone else encountered this?

QV11 SR5

thanks,

Steve

Re: Cannot Select Items in a List Box

giakoum — Tue, 03 Mar 2015 14:11:10 GMT

have you tried removing last document state?

Re: Cannot Select Items in a List Box

Tue, 03 Mar 2015 14:20:28 GMT

Yes. I tried removing the last document state yesterday, and again just now. It does not affect the problem. I also cleared the dashboard to be sure. thanks

Re: Cannot Select Items in a List Box

giakoum — Tue, 03 Mar 2015 14:22:18 GMT

locked fields? Can you share a sample app?

Re: Cannot Select Items in a List Box

Tue, 03 Mar 2015 14:37:21 GMT

No locked fields, either. Unfortunately, I cannot reproduce the issue in QV Desktop so sharing is not possible. I have some recent information that is pointing toward a section access issue (though I thought I had eliminated section access as the problem). Users with limited access are not experiencing this issue. Users with unlimited access now seem to have lost the ability to select this dimension.

The dimension that is a problem is Sales Person. That happens to be a dimension associated with section access. The business rule is sales persons see only their data, while the sales directors and developers like me see all the sales persons collectively. We can see them all collectively, but when selecting one or more, QV fails to execute the selection.

Re: Cannot Select Items in a List Box

sasikanth — Tue, 03 Mar 2015 14:39:12 GMT

hi,

is it a calculated DIM ?

Re: Cannot Select Items in a List Box

giakoum — Tue, 03 Mar 2015 14:41:20 GMT

That makes sense then. Try to remove section access completely, even the settings in the document --> opening part.

Re: Cannot Select Items in a List Box

simenkg — Tue, 03 Mar 2015 14:48:20 GMT

Did you recently remove a field with "Always one selected value" enabled?

I experienced some time ago that this somehow remained in one of the users sessions even though the field no longer existed and caused this behavior. The solution was to delete the models .Meta and .Shared files in the Accesspoint folder. Take note that this will remove any bookmarks the users have made. You should back them up before trying.

Re: Cannot Select Items in a List Box

JonnyPoole — Tue, 03 Mar 2015 15:37:43 GMT

Another idea:

You can get strange behavior if you have any multiple actions/triggers because the order of execution on the server differs from the client. This could cause strange selection behaviour because of something else trying to happen at the same time.

It doesn't explain why things broke but that is an area that comes up as being strange

Re: Cannot Select Items in a List Box

Tue, 03 Mar 2015 17:23:07 GMT

sasikanth, the dimension is not calculated. It is loaded from the data model.

Re: Cannot Select Items in a List Box

Tue, 03 Mar 2015 17:29:35 GMT

Simen, there have been no changes in months. It's interesting to hear that features can persist on the server or that, as Jonathan mentions, order of execution can create unpredictable behavior.

Re: Cannot Select Items in a List Box

JonnyPoole — Tue, 03 Mar 2015 17:42:45 GMT

As far as order of operations , its a tricky subject.

You'll find some info here on it. Trying to see if i can get you something more definitive to read up on. Anyways this pertains to actions/triggers specifically so not to worry if you aren't using those.

http://community.qlik.com/message/264053#264053

Re: Cannot Select Items in a List Box

Tue, 03 Mar 2015 18:05:59 GMT

ioannis, I am glad you suggested the unchecking the setting in document > open. I forgot to do that. Unfortunately, it had no effect.

Re: Cannot Select Items in a List Box

Tue, 03 Mar 2015 20:17:54 GMT

This afternoon web access was lost for a few minutes ("Message: No Server" was displayed on the AccessPoint), and when it came back, poof, the issue was resolved! Our server folks have not found an issue in the logs. They were doing nothing on their end to cause a disruption.

Thanks for the suggestions. I wish I knew how and why this resolved itself.

Re: Cannot Select Items in a List Box

kkorynta — Tue, 12 Sep 2017 18:27:22 GMT

I just had a similar issue with v12.1 SR3 and wanted to share how I resolved it.

The issue was that one of our bookmarks was utilizing a field that was locked to a specific value. The underlying data on that field changed and that value was no longer a value that could be selected. While the 'current selections' box did not show this particular field, the lock persisted, thus making the list box unclickable.

The quickest way to fix this is to go to the "navigation" menu bar and click the "unlock" button. This will unlock all fields, including fields that are not visible from the current selections box.

Re: Cannot Select Items in a List Box

Wed, 13 Sep 2017 13:13:49 GMT

Thanks. That is a great find. The issue recurred for us until we did a thorough revision of the dashboard. We did away with a locked field, among other things we no longer needed, and it fixed the issue for good for us. I did not know for sure which change worked, but your observation paints the locked field as the culprit!