Disable always one selected value on Qlik Sense

[Aurelien_Martinez]

Hi community,

I have a QlikView application with one field with "Always One Selected Value" option. After migration to Qlik Sense I can not select value in this field and I can not remove this option.

Do you have an idea to solve this issue?

cf my application.

Thanks .

Best Aurélien.

[Giuseppe_Novello]

I could say this would be a possible bug from transferring a Qlikview listbox that has enable "Always One Selected Value" to a QVF or QlikSense document. @Michael Tarallo Josh Good would you agree?

Or not sure you have a workaround?

Gio

[Michael_Tarallo]

Yes - I will log with R&D

Mike

[Michael_Tarallo]

Question - how did you migrate? - What version of Qlik Sense are you using, the latest Qlik Sense Desktop a Beta version? Did you use the older migration tool?

Currently with the latest version of Sense - we only migrate the data, script and data model and know chart or selection objects.

This information will help us understand more about this issue.

See these links for reference:

Qlik Sense Desktop - Loading Data from QlikView Applications (video)

Qlik Sense Desktop - Converting a QlikView Data Model (video)

Mike

[Giuseppe_Novello]

Thank you Michael! I will log it.

Aurelien - Thank you for informing, stay tune for future release that might have the fix implemented.

Gio

[Michael_Tarallo]

Hello Aurélien, I updated the thread - please let us know the process you took and include screen shots.

Thanks

Mike

[Giuseppe_Novello]

Aurelien,

Before I go further, I would follow Michael Tarallo videos that he attached and see if you can still replicate the issue.

Gio

[JonnyPoole · Accepted solution]

Perhaps its obvious but the short term workaround would be to uncheck it in QV first and save as a new copy (pre-migration copy) and migrate the altered one.

... at least until we have fixed up in the product.

[Aurelien_Martinez]

Thanks.

See how I do the migration and I am using 0.96.0 build 23

Aurélien

[Michael_Tarallo]

Perfect, love the video. Completely clear now. As you can see - one would think setting an option on a list box, would not bring this behavior over - if we only moved the script, the data and the model over.

So this has been logged.

Thanks for your effort.

See what Jonathan recommended if applicable as a work-around.

Mike