# How to get relation-dependent display of fields (conditional fields)

**URL:** <https://community.fibery.io/t/how-to-get-relation-dependent-display-of-fields-conditional-fields/5564>\
**Category:** Get Help\
**Created:** [December 20, 2023, 6:07pm UTC](https://community.fibery.io/t/how-to-get-relation-dependent-display-of-fields-conditional-fields/5564 "2023-12-20T18:07:13Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\
**Post date:** [December 20, 2023, 6:07pm UTC](https://community.fibery.io/t/how-to-get-relation-dependent-display-of-fields-conditional-fields/5564/1 "2023-12-20T18:07:13Z")

</div>

Use case: I have more than hundred databases and want to reduce them to optimize and make my spaces less complex. The strategy for this is to have a generic database ‘Page’ with a relation to database ‘Page type’. All content that does not require unique fields, thus can become a Page with a specific Page Type.

However, I like particular fields (relations) of the Page database ony to show up if it is of a particular Page Type.

For example, only if a page is of type ‘Research Paper’, I like to show the Author and Abstract field.

How can I accomplish this?

---

<div class="post-metadata">

**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 20, 2023, 6:09pm UTC](https://community.fibery.io/t/how-to-get-relation-dependent-display-of-fields-conditional-fields/5564/2 "2023-12-20T18:09:05Z")

</div>

You can’t.  
This would be an example of showing/hiding field being dependent on the value of another field, and this is not currently possible.

---

<div class="post-metadata">

**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 20, 2023, 6:10pm UTC](https://community.fibery.io/t/how-to-get-relation-dependent-display-of-fields-conditional-fields/5564/3 "2023-12-20T18:10:02Z")

</div>

The closest you can achieve is to use pinned fields and have them set to hide when empty.

---

<div class="post-metadata">

**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 20, 2023, 6:13pm UTC](https://community.fibery.io/t/how-to-get-relation-dependent-display-of-fields-conditional-fields/5564/4 "2023-12-20T18:13:00Z")

</div>

This

> [@Yuri\_BC](#):
>
> All content that does not require unique fields, thus can become a Page with a specific Page Type.

and this

> [@Yuri\_BC](#):
>
> I like particular fields (relations) of the Page database only to show up if it is of a particular Page Type.

are basically contradictory.

Fibery does not support the concept of type-based inheritance.

---

<div class="post-metadata">

**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\
**Post date:** [December 20, 2023, 6:23pm UTC](https://community.fibery.io/t/how-to-get-relation-dependent-display-of-fields-conditional-fields/5564/5 "2023-12-20T18:23:44Z")

</div>

You are right that it sounded contradictory. What I mean is that when consolidating databases to reduce the amount of databases, I make a choice which ones really need their own database because of relatively many unique fields, and which ones can use the same generic Page database because they only have a few unique fields.

Anyway, this topic is part of an attempt to reduce complexity of Fibery whilst retaining flexibility and intuitive user experience.

I can imagine that fibery and users have discussed this before, and maybe there are some best practices documented for and optimal architecture of a space, depending on the use?

---

<div class="post-metadata">

**Author:** ![njyo](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/njyo/32/923_2.png) [@njyo](https://community.fibery.io/u/njyo)\
**Post date:** [December 20, 2023, 6:35pm UTC](https://community.fibery.io/t/how-to-get-relation-dependent-display-of-fields-conditional-fields/5564/6 "2023-12-20T18:35:33Z")

</div>

If Fibery supports inheritance, this would be possible:

> [@FRQ: Database Inheritance](https://community.fibery.io/t/frq-database-inheritance/4528):
>
> Hi, For certain types of databases (i.e. Tasks, People, Organisations, Tools) I would like to have the ability to inherit/extend databases. For example: I want a base database called Person which has a few basic fields: given name, surname, email, phone, etc. I’ll have database called Staff that extends Person, which in addition has fields like: join date, role, salary, etc. I’ll have a database called Contact that extends Person, which adds fields like: company, meetings, etc. I’ll have a d…

---

<div class="post-metadata">

**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:** [December 20, 2023, 9:28pm UTC](https://community.fibery.io/t/how-to-get-relation-dependent-display-of-fields-conditional-fields/5564/7 "2023-12-20T21:28:43Z")

</div>

Related: [Individual Layouts for a node, hide fields etc](https://community.fibery.io/t/individual-layouts-for-a-node-hide-fields-etc/995)

And it has 28 Votes! 😲
