asked on September 10, 2025
Hello,
I'm setting the expandAll: true and rows properties with the rows I don't want to be expanded in my report and it's working correctly, but when I remove a field and add another, the report seems to get lost.
JSFiddle reproducing the problem:
⋅ September 11, 2025
Hello,
Thank you for reporting this issue.
We were able to reproduce it on our side. We will investigate this behavior and provide a fix so that the expands would work correctly by negating the expands applied by the expandAll after the field change. The fix will be included in one of the upcoming minor releases, ETA Sep 29th.
Feel free to contact us if more questions arise.
Best Regards,
Maksym
⋅ September 30, 2025
Hello,
We are glad to announce that the issue when expandAll did not affect hierarchy levels with a single empty value was fixed.
This is included in the 2.9.113 version of Flexmonster: https://www.flexmonster.com/release-notes/version-2-9-113/
You are welcome to update the component. Check out our updating tutorial for guidance: https://www.flexmonster.com/doc/updating-to-the-latest-version/
Please tell us if the fix works.
Best regards,
Maksym
⋅ September 30, 2025
Hello, thank you for the feedback.
I tested the solution, but the problem demonstrated in the attached gif still persists.
⋅ October 3, 2025
Hello,
Thank you for getting back to us and for testing the fix.
It seems that the issue was not fully resolved, and the collapses are still being reset after changing the lower field. However, the exact problem from your previous GIF cannot be reproduced anymore. Now, the “Virginia” cell expands correctly after changing the field instead of appearing expanded but not showing the lower hierarchy.
Our team will research this behavior and provide a fix, ETA Oct 13th.
Please let us know if more questions arise.
Best regards,
Maksym
⋅ October 3, 2025
Hello, well noticed. The behavior has indeed changed. However, the report starts with:
{
expandAll: true,
rows: [{
tuple: ["geography.[california]"]
}, {
tuple: ["geography.[virginia]"]
}]
}
and after changing the fields it ends up removing the exceptions and resulting in all rows being expanded:
{
"expandAll": true
}
Shouldn't these exception lines be kept?
⋅ October 3, 2025
Hello,
Thank you for your reply.
You are right - the expanded cells should not collapse after the field below changes. Your comment assures us that we are on the same page about the expected behavior. We will work on adjusting the functionality so that the collapse exceptions remain intact after changing the fields.
Best regards,
Maksym