I'd like to have the possibility to define a tree structure in the table component based on 2 columns (master and detail).
this would allow to build a treegrid.
This would be very convenient for any spreadsheet based on a general ledger or bill of material or any hierarchy extracted from an ERP.
out of very expensive FP&A solutions, there's nothing to handle GL related data entry in the cloud.
Depends how deep the hierarchy needs to go. There is the expandable row feature. If you add another table there perhaps that might work. I'm not sure a table is supported. But a keyvalue list is.
Here's an example. The data in the expandable row can hold a container. Which can display a collection of child data. I'm not sure if this can be done dynamically by using javascript. Perhaps someone who knows more about the expandable row could give us more insight.
the main issue is that a GL hierarchy or a BOM hierarchy is not a balanced hierarchy.
Basicaly, I'm looking for a treelist that would be a merge between the table component and the checkbox tree component with 2 new features : hidding empty levels on grouping and a transitive closure based on 2 columns of the table.
So far I feed the table with a recursive query from the retool database and use grouping options in the table component but the empty levels can't be hidden when the hierarchy is not balanced.
I had another user make a similar feature request for 'table tree' component that would be a combination of the checkbox tree and a table component.
I can tag this thread in as a +1 in support of that feature and keep you updated on any news I hear from the engineering team
Thank you so much for sharing the information about the lack of tools to handle GL related data entry and the details about GL/BOM as we are looking to help expand our use cases for manufacturing clients and this sounds like exactly something that would be very useful for those and many other use cases.
@Steven_WHere are the docs on expandable rows! This was the same suggestion I had for the other user who was hoping to build a tree grid component as it is likely the closest current functionality we have.
Financial planning solutions is a market with no actual innovation since the release of TM1 on 1982.
A lightweight solution based on client side olap cube with write back on top of a centralised retool database would kill all the "spreadsheet sharing" solutions.
Thank you so much for providing these Github repros and explaining this gap in the financial planning solutions market!
I had no idea that the market was so ready for a better tool and think Retool could be the perfect fit to implement this. I will show this to our product team as they will likely want to see this.
We absolutely love great feedback like this for expanding Retool use cases and helping serve our customers!