Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in Toronto Sept 9th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
dpduran
Contributor III
Contributor III

bug in listbox not populating one new value until service restart

Hello,

has anyone faced this issue?

A listbox does not populate one new value in listbox through web access point using AJAX.

The value does display through Desktop client, but when reloaded with Publisher the data is there but the value is not shown in the listbox.

Listbox is a plain and simple listbox without expressions of any kind... the field used in the listbox does not have empty values, and all data has string values... can't be more simple.

Could this be related to bug 53967 ? We're on 11.20.12904.0

The issue happened in 2 diferent servers same version, only fixed after services were reloaded.... can't be a problem with the file since it's correctly shown when opened through Desktop client.

Funny thing is you can see it populating the value when related selections are made, then the value is shown in the listbox as only possible value but not selectable...

Labels (5)
6 Replies
rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

It could be related to session state.  Try "remove last document state" (under "View Details" in Access Point.

-Rob

dpduran
Contributor III
Contributor III
Author

Hi Rob, this was also tested, forgot to mention it in the post, with no luck.

We also removed any shared and meta file generated by the doc to check, and that didn't work either.

The only thing that worked after all was restarting the services...

rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

Is "Always One Selected" on for the field?

-Rob

dpduran
Contributor III
Contributor III
Author

nope, is as simple as a list box displaying all values from one field, no expressions, no formatting... it simply does not show the value when accessed through accesspoint, it does with Desktop editor, and it's just with one value.

After the services are restarted, it simply populates that value along with the others in the listbox from then on... it happened in our Test server first time, then our production publisher showed the same behaviour, after restart was solved.

If you do any other selections that would, by context, get that field shown in the listbox as the only possible value, it will show but can't be selected in any way.

elyM
Partner - Creator
Partner - Creator

Hi Diego,

we have found similar behavior affecting our customer's production environment (11.2 build 12758).

Same QlikView version into test environment doesn't propose this issue.

All QikView documents affected have at least one field with properties "always one selected" .

We have made deep control about :

  • qvw
  • shared (no corruption found)
  • ACL table (we have NTFS Authorization)
  • open in different browser (chrome, mozilla firefox, IE11)
  • open through QVP protocol
  • open some case to support@qlik.com (can't reproduce -> closed case)
  • ask to Global Enterprise Architect

but no result.

The only way to resolve was to restart QVS service.

Kind Regards,

Ely

dpduran
Contributor III
Contributor III
Author

That was my feeling, since we can't reproduce the error, we won't be getting anything back from support....

This doc has indeed some other listboxes with "Always one selected value" checked but nto this one, how would this be affecting? I mean, I now it could affect about possible selections if Always one selected value was filtering the data model though.

Thng is this listbox is as plain as I described above, no special stuff marked, just a plain listbox supposedly showing up all values within the field selected, just that.

Even if it was not selectable, it should be shown in the list but greyed out. but it doesn't. And when it's shows as the only related option of that field with current related selections done to other fields, it can't be selected! It's crazy...

And indeed the only solution was to restart QVS...