# Field available in database based on another field

**URL:** <https://community.fibery.io/t/field-available-in-database-based-on-another-field/4568>\
**Category:** Get Help\
**Created:** [June 7, 2023, 5:51pm UTC](https://community.fibery.io/t/field-available-in-database-based-on-another-field/4568 "2023-06-07T17:51:09Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![tycecycle](https://avatars.discourse-cdn.com/v4/letter/t/848f3c/32.png) [@tycecycle](https://community.fibery.io/u/tycecycle)\
**Post date:** [June 7, 2023, 5:51pm UTC](https://community.fibery.io/t/field-available-in-database-based-on-another-field/4568/1 "2023-06-07T17:51:09Z")

</div>

Is it possible to only make a field available based on another field? I’m not talking about simply toggling the visibility of the field on or off, I mean something like the following:

Two fields named 1 and 2.

Possible values in field 1 are A and B.

Possible values in field 2 could be anything.

If field 1 has A selected, field 2 is a field that is available for the entity/row. If field 1 has B selected, field 2 is not available for the entity/row.

The use case is to have relationships from lots of different databases to one database without having the visual clutter of seeing irrelevant fields for entities. Like if I have a db that has relationship fields to ten other dbs, but at most an entity will only have one of the ten relationships, I don’t want to see all ten fields on that entity. Even if I live the nine irrelevant fields blank, just feels like extra noise.

Hopefully that’s clear!

---

<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:** [June 7, 2023, 6:31pm UTC](https://community.fibery.io/t/field-available-in-database-based-on-another-field/4568/2 "2023-06-07T18:31:23Z")

</div>

> [@tycecycle](#):
>
> Is it possible to only make a field available based on another field?

It’s not possible, no.

> [@tycecycle](#):
>
> Like if I have a db that has relationship fields to ten other dbs, but at most an entity will only have one of the ten relationships, I don’t want to see all ten fields on that entity.

In some situations, this is better solved with linked highlights/back refs rather than structured relations

---

<div class="post-metadata">

**Author:** ![tycecycle](https://avatars.discourse-cdn.com/v4/letter/t/848f3c/32.png) [@tycecycle](https://community.fibery.io/u/tycecycle)\
**Post date:** [June 7, 2023, 6:47pm UTC](https://community.fibery.io/t/field-available-in-database-based-on-another-field/4568/3 "2023-06-07T18:47:33Z")

</div>

I’ll experiment with highlights/back refs and see if that accomplishes what I’m looking to do. Thanks!

---

<div class="post-metadata">

**Author:** ![tycecycle](https://avatars.discourse-cdn.com/v4/letter/t/848f3c/32.png) [@tycecycle](https://community.fibery.io/u/tycecycle)\
**Post date:** [June 13, 2023, 2:41pm UTC](https://community.fibery.io/t/field-available-in-database-based-on-another-field/4568/4 "2023-06-13T14:41:05Z")

</div>

For posterity, “live” is a typo in the og post. Should have been “leave”.