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

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
mphekin12
Specialist
Specialist

Sorting Issue

I have a list box that is sorted by State and then by Text A -> Z.  When I open the .qvd directly, the sort is working correctly.  When I publish the qvd and open it via 'Open in Sever', sometimes the list box is only sorted by Text A - Z, the state is totally being ignored.  If I make a copy of this object and paste it in the dashboard without making any changes to the properties, the pasted version is sorting by State and then by Text A - Z. 

Has anyone else experienced this?  Does anyone know of a work around?  I am using QV 11.

I have included a screen shot of the two list boxes.  The one on the left is the original and the one on the right is the copy.

Thank you!

5 Replies
mphekin12
Specialist
Specialist
Author

FYI, it looks like I might have found a solution.  I changed the State sort criteria from 'Auto Ascending' to 'Ascending' and so far the sorting seems to be working correctly on the server.

Not applicable

Personally, I think there is a bug in the Auto Ascending on State (I'm using QV11 SR1).

Most of my list boxes are Auto Ascending and until recently, they behaved as expected.

However, recently they sometimes display with all the available selections at the top and sometimes with them scattered throughout the long list of values.

I can't figure out why this has happened, but it has affected all my documents - both on the server and on the desktop. The fix is to change to Ascending, but this isn't good enough and I hope Qliktech investigates this issue.

James

mphekin12
Specialist
Specialist
Author

I agree with you James.

Not applicable

i have the same problem and setting sort state of listbox to ascending isn't working for me.

do you know if this issue exist in SR2?

is there another workaround for it?

Not applicable

We've recently upgraged to 11.2 SR1.

I can't manage to replicate the problem, which could mean it has been fixed. However, if it turns out this is not the case I will post again to this thread.

James