Skip to main content
Announcements
NEW: Seamless Public Data Sharing with Qlik's New Anonymous Access Capability: TELL ME MORE!
cancel
Showing results for 
Search instead for 
Did you mean: 
SreeniJD
Specialist
Specialist

Always One Selected Value behaving strangely

Hi Gurus,

We have been replicating an excel dashboard in QV and to replicate exact behavior we have used many alternate states. For one of the field we have checked "Always one selected value" property, however later field was removed and added again to the sheet. We were not able to get the selected value in the multibox. After couple of hours of R&D we found that the field property was still set to "Always one selected value". Is this a BUG or expected behavior?

Thanks in advance,

5 Replies
PrashantSangle

Hi,

did you applied alternate state to the field which you have created and applied "Always One Selected Value" and then deleted.

If that was the case it is behaving as per expected.

Regards

Great dreamer's dreams never fulfilled, they are always transcended.
Please appreciate our Qlik community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved 🙂
SreeniJD
Specialist
Specialist
Author

Thanks for the quick reply - I have used only inherited state, but not applied alternate state to the field

Anonymous
Not applicable

May be QV is so smart that it didnot overwrite the stored state of that particular field.

jonathandienst
Partner - Champion III
Partner - Champion III

The 'always one selected' property is a property of the field and not a property of the list box- even though the interface for enabling it is in a list box (or multibox). So if the list box for a field is deleted and the later recreated, the setting will be retained.

In the same way, if another list box is created for the same field, it will follow the 'always one selected' setting in the first list box. Changing either one will also change the other.

So, no, this is not a bug.

Logic will get you from a to b. Imagination will take you everywhere. - A Einstein
SreeniJD
Specialist
Specialist
Author

If not a BUG, is it a limitation of QV as we will generally don't know what were the properties that were set to the deleted fields(in this case list boxes, multi boxes). Ideally properties should be applicable to the listbox but not to the original field.

Thanks,

Sreeni