# 3 Level Hierarchy table with single-select **URL:** \ **Category:** Get Help\ **Created:** [December 21, 2023, 12:51pm UTC](https://community.fibery.io/t/3-level-hierarchy-table-with-single-select/5573 "2023-12-21T12:51:11Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Mr.Ricky](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mr.ricky/32/8422_2.png) [@Mr.Ricky](https://community.fibery.io/u/Mr.Ricky)\ **Post date:** [December 21, 2023, 12:51pm UTC](https://community.fibery.io/t/3-level-hierarchy-table-with-single-select/5573/1 "2023-12-21T12:51:11Z")
Hi everyone, I’m new here and I hope this is the correct section to write in. I’m not a programmer and I struggle to think on an abstract approach. But I tried 🙂 I have done many tests: complex and simpler and I have come very close to what I would like to achieve but I have never achieved the full objective. I need to obtain a table in which the person doing the data entry cannot make insertion errors. What I need to create is a three-level hierarchical structure, where the selection of who will enter the data is filtered at each level based on the parent’s choice. So, the selection will have to be with a single-select. The structure is practically this: - 1 – 1.1 ---- 1.1.1 ---- 1.1.2 – 1.2 ---- 1.2.1 ---- 1.2.2 - 2 – 2.1 ---- 2.1.1 ---- 2.1.2 – 2.2 ---- 2.2.1 ---- 2.2.2 etc. Thank you thank you 🤗 ---
**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:** [December 21, 2023, 1:14pm UTC](https://community.fibery.io/t/3-level-hierarchy-table-with-single-select/5573/2 "2023-12-21T13:14:35Z")
> [@Mr.Ricky](#): > > I need to obtain a table in which the person doing the data entry cannot make insertion errors. Do you mean that you want to create a table view of entities? > [@Mr.Ricky](#): > > the selection of who will enter the data is filtered at each level based on the parent’s choice. Can you explain what you mean by this? ---
**Author:** ![Mr.Ricky](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mr.ricky/32/8422_2.png) [@Mr.Ricky](https://community.fibery.io/u/Mr.Ricky)\ **Post date:** [December 21, 2023, 6:00pm UTC](https://community.fibery.io/t/3-level-hierarchy-table-with-single-select/5573/3 "2023-12-21T18:00:37Z")
Hi Chris, Yes, I would like to get a table view with entities: - Nane - Single-Select in which to select a level 1 item - Single-Select which shows a list of level 1 child, from which to select an item - Single-Select which shows a list of level 2 child, from which to select an item The Singles-Select lists should only show items related to the parent. So, if in the first enity (Level 1) I select 1 in the second entity I will just see 1.1, 1.2, … Same concept for the Level 2: if I select 1.3, in Level 3 i Will see 1.3.1, 1.3.3, … In this way, whoever enters the data cannot incorrectly mix children and parents. Ty ---
**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:** [December 21, 2023, 6:29pm UTC](https://community.fibery.io/t/3-level-hierarchy-table-with-single-select/5573/4 "2023-12-21T18:29:46Z")
If I have understood correctly, I think what you want to do is possible with databases (not single selects) combined with relation filters. Here’s how it would work: Level 1 db relates 1:m to Level 2 db Level 2 db relates 1:m to Level 3 db ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/8/8bef03f5869deb3c0be19925ba1946d66fbba9d9.png) Here is an example of how the actual entities might be related: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/d/ddb87f3e52aafce784869da7c27834547bf575ef.png) Now, an Item can link to a single Level 1 entity, a single Level 2 entity and a single Level 3 entity: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/a/a1ef53876b5feb244325ad8afbce7edbc5421bf6.png) For the L2 and L3 relations, you should set relation filters that only allows a user to choose something based on the value of the level above value: ![firefox_PGtjWJXbSs](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/8/8bba4a4d4beda46886ab96dd1d0e3d8e121ecdb9.gif) When this is done, choices will be limited: ![firefox_IKW3IqDFHI](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/a/a240ab6126db41f840a9b5cfa1171f801e037348.gif) Note however, it doesn’t prevent a user from making a set of choices, and then changing a higher level value which would ‘break’ the rules: ![firefox_VoHyCsweJw](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/f/fe001032225ea2573b734dae35253a56e5a618a4.gif) If that is important, you may want to add automation rules that clear the value of a lower level field when a higher level field is changed: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/4/4d565b5a221c0de708cba86cbd54301c186f3e88.png) and ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/224b88eda0ea5e484a9ed857c02e66848553c6ae.png) Then you get this: ![firefox_KSn6cy9Sgi](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/203ea1cfe8a9d661e9b3caed32c89be6197f6505.gif) ---
**Author:** ![Mr.Ricky](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mr.ricky/32/8422_2.png) [@Mr.Ricky](https://community.fibery.io/u/Mr.Ricky)\ **Post date:** [December 21, 2023, 7:18pm UTC](https://community.fibery.io/t/3-level-hierarchy-table-with-single-select/5573/5 "2023-12-21T19:18:36Z")
Oh thanks Chris… From the final video, I believe that’s exactly what I’d like to achieve. In the next days, I’ll follow your procedure. Thank you 😉 ---
**Author:** ![Mr.Ricky](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mr.ricky/32/8422_2.png) [@Mr.Ricky](https://community.fibery.io/u/Mr.Ricky)\ **Post date:** [December 21, 2023, 9:33pm UTC](https://community.fibery.io/t/3-level-hierarchy-table-with-single-select/5573/6 "2023-12-21T21:33:36Z")
Thanks Chris, great, you were very kind. Simple and effective solution. Im so happy 🤗