# \[DONE\] Individual Layouts for a node, hide fields etc

**URL:** <https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995>\
**Category:** Ideas & Features\
**Tags:** entity-view\
**Created:** [September 18, 2020, 8:51am UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995 "2020-09-18T08:51:36Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [September 22, 2020, 3:26am UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/13 "2020-09-22T03:26:23Z")

</div>

Hi Guys,

I believe you are getting onto the subject that has been frequently discussed: A way to reduce the number of fields that show when you have a plethora of Relations to a Type - to put it in more simple terms (which I hope I did!).

Here is one of the better previous convos on the subject, with @Polina_Zenevich in fact weighing in:

> [@Conditional fields in apps](https://community.fibery.io/t/conditional-fields-in-apps/757):
>
> This seems like such a no-brainer I’m wondering if somebody already asked it and I missed it (sorry if that’s the case). It would be great to have a way to make fields invisible unless another field has value X or Y, otherwise apps have a tendency to quickly get bloated. Congrats for all the good work and wish you all the best. Keep your sense of humor

@Oshyan, when you mention here:

> [@Oshyan](#):
>
> rather than having each variation of a View be a separate item in the left menu, like ClickUp or Notion you could select different saved and named Field views and Sort options from a dropdown or similar.

and touch on Notion, I think that is one of the biggest flaws of Notion, solved only somewhat by Fibery until there is a solution for handling unused Fields. Notion has the negative of a hugely long page when you add relations, which becomes redundant when you add a Linked Database, which in fact you need to do to get a lot of the benefit in Notion.

If Fibery could solve 1) the situation with unused Fields that _must_ at the moment exist when you create a relation, and 2) more ability for “Collections” (that’s the proper term for the many-to-many groupings in an Entity’s details area) to behave like Subtables - for example inline edit - then there is a real benefit over Notion here. This is something that would really help me with my use of Fibery and the whole UX of your app.

And I can’t comment here without thinking of our old friend [Polymorphic Relations](https://community.fibery.io/t/polymorphic-relations-when-creating-relation-ability-to-have-entire-app-from-which-to-choose-and-not-just-type/425/15), since their existence vastly reduces the need for so many fields. And again @Oshyan in that post, you said Conditional Fields would be helpful here. Very true, too! I have many instances when I have a dropdown that if I select one value, I’d like to have a related dropdown field that would either 1) only show up if that value is chosen, or 2) show some filtered options based on the value in the first dropdown. I believe Coda can handle the latter scenario with Formula Filters, so perhaps that’s something Fibery might get sooner than later?

Hope that’s a useful contribution guys!

---

_[View the full topic](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995)._