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: [image] Here the hierarchical option is not available for the same DB when it appears at the second level: [image]

This is resolved in latest release [image] Feb 1, 2024 / selfie Add self-relations on any levels in Views, Format date and time setting, Custom access templates Changelog selfie Add self-relations on any levels in Tables, Lists and Smart Folders Now you can visualize recursive relationships at any level in List, Table and Smart Folder. For example, if you have Product Areas (nested) and Features (nested), you can see them like this Product Area 1 - Product Area 1-1 - Feature 1 - Feature 1-1 - Feature 1-2 - Feature 2 Product Area 2 - ... Here is how it looks in a Table View: [image] NOTE: Don’t miss this self-relation icon in the view setting…

[image] Representing nested relations Ideas & Features 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 :person_shrugging:

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: [image]Representing nested relations 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 Start by building each databases’s nested structure first (which is what fibery does for the first level): [image] 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: [image] 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.

No "hierarchical" option in List views for second-level DB?

Get Help

mdubakov February 2, 2024, 7:52am 5

This is resolved in latest release

Topic		Replies	Views
Representing nested relations Ideas & Features	31	3925	February 12, 2026
Group by the same database relation - Also for deeper levels Ideas & Features	22	978	February 2, 2024
Hierarchical Relation Fields Ideas & Features flexible-domain	1	504	November 8, 2023
[DONE] Display recursive relationship (task -> subtask) when it's not the "first level"? Get Help	5	351	November 8, 2023
[DONE] Many-to-many relationships should be usable for levels in lists Ideas & Features list-view	24	3585	May 6, 2022

No "hierarchical" option in List views for second-level DB?

Related topics