# No "hierarchical" option in List views for second-level DB? **URL:** \ **Category:** Get Help\ **Created:** [February 23, 2023, 6:44pm UTC](https://community.fibery.io/t/no-hierarchical-option-in-list-views-for-second-level-db/4049 "2023-02-23T18:44:24Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [February 23, 2023, 6:44pm UTC](https://community.fibery.io/t/no-hierarchical-option-in-list-views-for-second-level-db/4049/1 "2023-02-23T18:44:24Z")
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](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/d/da31ddb6787352d17183f6987e14ca8da3f4274e.png) **Here the hierarchical option is not available for the same DB when it appears at the second level:** ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/2e4be2be074fc552eec15cb1c8b26db42baab017.png) ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [February 23, 2023, 6:56pm UTC](https://community.fibery.io/t/no-hierarchical-option-in-list-views-for-second-level-db/4049/2 "2023-02-23T18:56:41Z")
> [@Representing nested relations](https://community.fibery.io/t/representing-nested-relations/1405/11): > > 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 🤷 ---
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [February 23, 2023, 7:08pm UTC](https://community.fibery.io/t/no-hierarchical-option-in-list-views-for-second-level-db/4049/3 "2023-02-23T19:08:54Z")
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. ---
**Author:** ![cannibalflea](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/cannibalflea/32/318_2.png) [@cannibalflea](https://community.fibery.io/u/cannibalflea)\ **Post date:** [September 13, 2023, 11:38pm UTC](https://community.fibery.io/t/no-hierarchical-option-in-list-views-for-second-level-db/4049/4 "2023-09-13T23:38:20Z")
I offered a possible way of achieving [this here](https://community.fibery.io/t/representing-nested-relations/1405/15): > [@Representing nested relations](https://community.fibery.io/t/representing-nested-relations/1405/15): > > 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](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/e/eded7061ff2bd0208fd114e27ca4a231642525c8.png) > > 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](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/f/f72a035cab274e588452403b69bc6b7cdc5b9e70.png) There was also a discussion [further down the same thread](https://community.fibery.io/t/representing-nested-relations/1405/22) 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. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [February 2, 2024, 7:52am UTC](https://community.fibery.io/t/no-hierarchical-option-in-list-views-for-second-level-db/4049/5 "2024-02-02T07:52:33Z")
This is resolved in latest release > [@Feb 1, 2024 / selfie Add self-relations on any levels in Views, Format date and time setting, Custom access templates](https://community.fibery.io/t/feb-1-2024-add-self-relations-on-any-levels-in-views-format-date-and-time-setting-custom-access-templates/5780): > > 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: NOTE: Don’t miss this self-relation icon in the view setting…