Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Straight Table Sorting Problem

Hello,

I have a problem with the sorting in my straight table- everything works normally as long as I do not use an expression in the 'background color' of my expressions or dimensions.  However, if I do add a background color expression to either the table dimension or any of the expressions, suddenly the sorting does not work at all.

Regardless of whether interactive sort is checked or not (and the priority of the expressions in the sort list), the sorting for the chart completely ignores everything except the dimension sort order.  In other words it becomes impossible to sort by any of the expressions (interactively or otherwise).

Using QV11SR2.

Any help or suggestions would be greatly appreciated.

--Ben

14 Replies
Anonymous
Not applicable
Author

I have this problem, too. Still exists in QV 11.2 SR12

I logged a support call for this. Will see what comes up...

Update 12-NOV-2015 Their response is that it is not possible to sort on a column containing a condition, and that you can propose to add the feature if you wish.

At the very least there should be a warning saying that the sort will not work when you select such a column...

Anonymous
Not applicable
Author

Come on Qlik, really?

Hope this will be fixed in QV 12

agni_gold
Specialist III
Specialist III

Is this bug corrected in qv12 ?

warfollowmy_ver
Creator III
Creator III

I'm just beside myself with anger.
This problem has not been solved until now. I ran into this. Tried to bypass the problem made a macro, it works great (https://community.qlik.com/t5/QlikView-App-Development/Change-sort-priority-in-straight-table-with-m...).
But with the trigger after opening at the end, the straight table still resets the sort. The report is up-to-date and updated frequently, so this is a pain for users.

Thanks QlikTech for having thrown QV and doing only QS.

warfollowmy_ver
Creator III
Creator III

In the end I managed to get around this problem.
I created a variable in the boot script LET Trigger = '= now ()';

I also made a trigger when changing the Trigger (variable) to run a macro (that is higher in the message) and reset the Trigger (variable).

This option works in contrast to the trigger when opening.