asked on August 18, 2023
Hello, we have a question regarding setTableSizes, and we're quite confused about it.
In our application, we have hooked the context menu up to the tableSizes object such that a user can right click a column or row and hide it dynamically (by setting height/width to 0). This has been implemented for a while and works perfectly. We just add the tuple of the given column/row to the tablesizes and refresh.
Recently, it was discovered that hiding a parent dimension does not impact children. We have had this feature for months now, and we are all certain that it used to be the case that setting a parent dimension's size to 0 would do the same for any children.
Has there been any change on FlexMonster in this part? Or has this always been the default behavior?
Thank you in advance 🙂
⋅ August 21, 2023
Hello,
Thank you for your question.
Please note that one table-size object always affects a single row or column, matching its tuple or row/column index. The children's hierarchies are not affected by the size set to their parent; this has always been a default component's behavior.
To hide children's columns or rows, additional logic should be implemented. In the handler responsible for hiding cells, you could use the getMembers API call to retrieve children cell's unique names. Later, these unique names can be used in setTableSizes to hide these rows or columns as well. Also, you could try using the "Exclude" tab of the cell's context menu, which will remove the selected member and its children from the grid. However, this feature will apply a filter to hide each member's occurrences instead of hiding a single cell while not affecting the others.
Please let us know if our answer helped you.
Best Regards,
Maksym
⋅ September 12, 2023
Hello,
Hope you are doing well.
Our team is wondering if you had time to try implementing the solution for collapsing a cell with its children
Please let us know if the provided information was helpful.
Best Regards,
Maksym
⋅ September 13, 2023
Hello
Not yet. Our developer is currently on vercation.
i will let him know about this when he returns.
Thanks /MAM
⋅ September 18, 2023
Hello again,
Unfortunately, get members is not accurate in all instances. However, we found a method to get all created dimensions at report-generation time. We store all dimension uniqueNames in a variable and get children dimensions and hide them through this.
Thank you for your help!
Br
Jonas
⋅ September 19, 2023
Hello, Jonas!
Thank you for your reply.
We are glad to hear that you were able to find the solution for collapsing the hierarchies with all their children.
Feel free to contact us if any other questions arise.
Best Regards,
Maksym
