Hi,
We are seeing that the sort order for some columns in pivot table is incorrect when the number of columns increases in the dataset. We are currently using version 2.8.24, and please find the attached report json which demonstrates the issue. As you can see in the attached screenshot, the date values are sorted in ascending order instead of the descending order as defined in the data set.
This doesn't seem to be a problem if the data set contains less number of columns, where the date values are sorted in descending order.
Thanks.
Chen Woo
Hello, Chen Woo,
Thank you for reaching out to us.
It seems that your issue is only reproducible using version 2.8.24. We suggest you updating the Flexmonster component to the latest version in order to fix the problem with the sorting.
Please let us know if it works for you. Feel free to contact us if other questions arise.
Kind regards,
Nadia
We are not ready to upgrade to the latest version yet, but I saw that version 2.8.33 has fixed the issue.
BTW, is there a flexmonster jsfiddle that allows loading of older version of the library? This will be helpful to verify if a problem exists in an older releases.
Thanks.
Chen Woo
Hello, Chen Woo,
Thank you for your response.
You can switch to the older versions using our CDN. Please see the following example on JSFiddle: https://jsfiddle.net/flexmonster/gwjmvqyd/.
Kindly note that you can check the migration guide from 2.8 to 2.9 when you are ready to update the component to the latest version.
Please let us know if the update to version 2.8.33 would work for your case. You are welcome to write to us in case further questions arise.
Kind regards,
Nadia
Hello, Chen Woo,
Hope you are doing well.
Our team is wondering if you found the solution helpful. Please let us know is there still anything we can help you with?
We will be glad to hear your feedback.
Kind regards,
Nadia
Hello, Chen Woo,
Hope you are doing well.
We were wondering whether you had a chance to try the suggested approaches. Could you please let us know if our response helped?
Kind regards,
Nadia
Sorry about the late response. Yes, upgrading to version 2.8.33 fixed the issue. You may close the ticket now. Thanks.
This question is now closed