I’ve been testing the filters field and I found out that filters in the slice -> reportFilters field (directly in the JS part) can’t be moved without some mess, they seem different from filters that you put manually into the filters field once the report is loaded.
I even tested it with the jsfiddle from the basic demo : https://jsfiddle.net/flexmonster/rkprvhhs/
What I did :
Thank you for reaching out to us and for providing a JSFiddle for illustration.
It seems we have managed to reproduce the issue on our end as well.
Please see the following screencast for illustration.
Could you please confirm if this is the case?
Our team will provide the fix to this issue in the minor release version with the ETA 1st of June.
Please let us know if further questions arise.
Thank you for your answer, I do confirm this is the issue.
Thanks for the incoming fix.
We are glad to announce that the issue with report filters not re-positioning by drag and drop to the last position was fixed.
This is included in the 2.8.8 version of Flexmonster: https://www.flexmonster.com/release-notes/.
You are welcome to update the component.
Here is our updating to the latest version tutorial for guidance: https://www.flexmonster.com/doc/updating-to-the-latest-version/.
Please let us know if everything works.
Our team is wondering whether our fix works for your case.
You are welcome to contact us in case any additional questions arise.
We are looking forward to hearing from you.
Looks like it has fixed the issue, thanks.
I’m running into another problem with filters this time, if I change the position in the filter bar, the filter applies (or not), depending on the position it has.
I hope you can reproduce because giving an exemple with my dataset will be impossible (sensitive datas).
Thank you for your feedback.
Concerning the issue with filtering you are currently facing, we want to inform you that a similar issue has been fixed in the recent minor update ETA 2.8.17.
We suggest updating the component and testing the filters’ behavior.
Please let us know if it works for you.
Otherwise, we want to ask you for more details about the bug. For example, can you trace some specific positions on which filters are not applied?
Our team is looking forward to hearing from you.
To be more precise, it seems that the fourth filter doesn’t do anything, no matter the filter.
Flexmonster is in production – it’s kind of a big bug so we need a solution ASAP – with the version 2.8.11, I’ll try to upgrade to the last version.
Thank you for providing us with details.
We would like to confirm that the issue with the fourth report filter has been fixed with a minor update 2.8.17.
It means updating to the latest version is going to resolve the problem.
Our team is looking forward to your feedback.
Indeed, thank you !