# Conditional fields in apps

**URL:** https://community.fibery.io/t/conditional-fields-in-apps/757
**Category:** Ideas & Features
**Created:** [June 10, 2020, 6:49pm UTC](https://community.fibery.io/t/conditional-fields-in-apps/757 "2020-06-10T18:49:13Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![Raphael\_Mizrahi](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/raphael_mizrahi/32/732_2.png) [@Raphael\_Mizrahi](https://community.fibery.io/u/Raphael_Mizrahi)
#### Post date: [June 13, 2020, 10:44pm UTC](https://community.fibery.io/t/conditional-fields-in-apps/757/3 "2020-06-13T22:44:21Z")

</div>

Thanks for the reply. In my humble opinion, this should rank high in your priorities because I do believe this to be a very important feature in many sectors.

For instance in real estate, there is a lot of data to collect for listings. A lot of it is conditional, i.e if it’s a house, we’re gonna need to fill field A and B, if it’s an apartment we need to fill C and D, and so on.

If your business has any kind of complexity with many data points, you end up with potentially dozens of fields. Having a string of empty, irrelevant fields makes it very bothersome for users to input data. And when a crm is bothersome it slows adoption.

You could find workarounds, like an option to hide a field if it’s empty, or allow users to fill simplified webforms with only a few select fields to create items, but it’s still going to be a problem in the long run.

Just my 2 cents

---

_[View the full topic](https://community.fibery.io/t/conditional-fields-in-apps/757)._