I don’t understand why the List view’s “Hierarchical” option for a tree-structured DB is only available if the DB appears at the top level of the List view:
Here the hierarchical option is not available for the same DB when it appears at the second level:
1 Like
Chr1sG
February 23, 2023, 6:56pm
2
Am I correctly interpreting that only top-level types within a hierarchical list are allowed to be recursive? Would it be possible to allow nested types to have recursive relations as well?
I’ve got two types, ideas and tasks (it’s sort of a simplified GIST approach). Ideas can have sub-ideas and sub-tasks. Tasks can also have their own sub-tasks. Currently I’ve got a list that shows nested ideas, but I can only make it show the first level of sub-tasks.
Can’t say that it answers the ‘Why?’ though
1 Like
In my case (probably the most popular case by far), I am modeling a strict tree structure with the one->many self-relation.
This case at least should not be problematic to support, unless adding a third List View level that might refer back to an already-displayed parent.
I offered a possible way of achieving this here :
I believe the simplest case would be to first start with the current database relation as the primary parent and if no relation is defined to the same database (i.e. relation is null), then we would go up one level and use that relation as the parent relation (if it exists). And so on up the levels until you get to the first level at which point if no relation exists, it gets captured under a “no parent” bucket.Approach
Then in step 2, you start from highest level and move up and try to map all the root/level 1 items in the lower level databases:
There was also a discussion further down the same thread on impacts on both 1-many and many-many relations.
I do hope there is a solution to this at some point as it allows for many interesting possibilities.
