I have run into another problem similar to a previous problem we had here.
That problem needed me to implement a workaround in my Custom Data Source API to return the aggs.keys object so that its keys are in the same order as they are specified in the input query object.
This was fixed some time ago and the workaround removed.
Now we've seen a new problem pop up when we use drillAll: true with a hierarchy in rows/cols: the member filter popup displays the hierarchy as a flat single level hierarchy with all members on level 1. With the original workaround back in, the members filter popup displays the hierarchy as expected.
Here's a minimal reproduction where you can toggle between returning the keys in the query order ("ordered", i.e. with workaround) or without a particular order ("unordered", i.e. without workaround).
Hello, Ezequiel!
Thank you for reporting this issue.
We have reproduced the described filtering behavior on our side.
Our development team will have a closer look at this case and provide you with the fix on the ETA December 27th.
We will notify you as soon as the fix is ready.
Before the fix is ready, you can use mentioned workaround with returning keys in query order.
Feel free to contact us in case of any other questions.
Regards,
Solomiia
Hello, Ezequiel!
Hope you are having a great week.
Our team is glad to inform you that the issue with the order of aggs[].keys
affecting the hierarchy structure was fixed.
The fix is available in the 2.9.41 version of Flexmonster: https://www.flexmonster.com/release-notes/version-2-9-41/.
You are welcome to update the component: https://www.flexmonster.com/doc/updating-to-the-latest-version/.
Please let us know if the fix works well for you.
Kind regards,
Solomiia
Thank you, I gave this a cursory test and it's working!
Hello, Ezequiel!
Thank you for your feedback.
We are glad to hear that the fix works well for you.
Feel free to contact us in case of any other questions.
Best regards,
Solomiia