I came across this scenario wherein when sorting is applied on column and we click on row Filter to apply the selected sort, it is not reflected in the FM report.
Steps to reproduce this problem:
Open fiddle: https://jsfiddle.net/flexmonster/rkprvhhs/
Apply ascending sort on column Quarter 1
Click on Country filter
Apply AZ sort and click Apply
Expectation -> Country should be sorted in ascending order
Actual -> no sorting applied on the report
Note: When we de-select AZ from Country filter and click Apply -> select AZ again and click Apply -> it works
I need to understand why this is the behavior.
Thank you for reaching out to us.
We want to explain that sorting by values does not reset soring by members. Instead of applying sorting by members, we suggest clearing sorting by values. It will restore the previously applied members sorting.
In its turn, the requirement to de-select sorting before applying it again is aimed to avoid applying sorting after filtering the field. Otherwise, the user could overwrite values sorting not intentionally while trying to apply the filter.
We understand that this behavior may be slightly misleading in some specific cases. Still, it is considered to be the most consistent behavior, and there are no plans to change it in the future.
Please contact us if other questions arise.
Thanks Illia for coming back.
So what I understand as per your explanation is this:
If filter is applied on member(in this case Country with A-Z sorting) and sort is applied on a column(in this case Quarter 1),
then we should clear the sort on column first(Quarter 1) and then apply A-Z sorting on filter(i.e. Country)?
Please note: In our case we are using custom double-click listener to reset the sort, which doesn’t clear sorting on pre-defined sorted columns:
You have also mentioned in the reset sorting thread that a fix for this is expected in June release.
Thank you for your feedback.
You are right about the fact that you will need to clear sorting by values in order to restore previously applied sorting by members. If you want to apply a new type of sorting by members (for example, reverted alphabetical order), you will not need to perform this extra step.
Concerning the mentioned issue with sorting, we want to confirm that the fix will be introduced in June. It will allow clearing predefined sorting using the context menu. In its turn, clearing sorting by double-clicking the cell is a custom functionality considered to be a workaround. It may be positively affected by the coming fix. Still, the fix itself is mainly aimed at the built-in functionality provided by the context menu.
We hope it helps.
Do not hesitate to contact us if other questions arise.
Can you please confirm the context menu as mentioned above is the one that is launched after right click on column (attached screenshot for reference)?
In our case we have disabled it for our custom menu purpose.
We would appreciate if the June release can incorporate clearing sort on predefined sorted columns using custom handling (double-click listener).
We want to confirm that you are right about the context menu demonstrated in the attached screenshot.
Could you please clarify what kind of custom menu is used in your case?
Is it the customized context menu provided by Flexmonster? In this case, you can simply preserve options responsible for sorting.
Or maybe the built-in menu is fully disabled with the aim of displaying some custom element?
Concerning the custom handler for clearing sorting, we are not ready to provide you with a determined answer. It is because the mentioned double-click handler is a custom feature added over existing functionality. Still, we will consider your request while implementing the fix.
You are right that we have disabled FM context menu completely and displaying our application specific menu on right click.
If you can provide a solution to clear sort on pre-defined sorted reports through custom handling then that would be great!