# How we handle a view with too many related entities **URL:** \ **Category:** Fibery Showcase\ **Created:** [June 8, 2025, 4:52pm UTC](https://community.fibery.io/t/how-we-handle-a-view-with-too-many-related-entities/8949 "2025-06-08T16:52:26Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Mircea\_Braescu](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mircea_braescu/32/9729_2.png) [@Mircea\_Braescu](https://community.fibery.io/u/Mircea_Braescu)\ **Post date:** [June 8, 2025, 4:52pm UTC](https://community.fibery.io/t/how-we-handle-a-view-with-too-many-related-entities/8949/1 "2025-06-08T16:52:26Z")
One of the core benefits of Fibery is how flexible and customizable it is. The flipside of that is that things can easily get messy and out of control, which is exactly what happened to us when it comes to the Task database. The Task as we have customized it in Fibery is by far the most used database. That is because almost everything ties to it: the operational side (worklogs, epics, sprints, runways), system modelling (intents, documents, user interface, etc) and more (feedback highlights, red flags, flow steps, etc) As such, we ended up with Tasks having relations to ~20 other databases and as a consequences of that, the Task view became a clusterfuck filled with mostly empty lists. ![iScreen Shoter - Fibery - 250608165133](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/e/e4e44a708e5491ead787ecfac1dd6b3dc08e8255.jpeg) To solve this issue, we made use of the fact that any of the lists we see in Fibery can be customized, including to display elements from more than one database. ![iScreen Shoter - Fibery - 250608184406](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/9/9e2d86fb3282ed61ff76d720e7c49b647cb35a8d.jpeg) And so we made a quick google sheet to decide how to group related entities. ![iScreen Shoter - Arc - 250608191806](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/357dc8c5a09d771a1a20900ca36b0990b8487946.jpeg) Finally, we put all of that together and we ended up with two lists, “Modelling Entities” and “Related Entities” that group most of the ~20 related databases in just 2 lists. This makes the Task view less noisy and much more easy to navigate, while still keeping the same functionality we had before. Here is how a Task view looked before: ![iScreen Shoter - Fibery - 250608165133](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/e/e4e44a708e5491ead787ecfac1dd6b3dc08e8255.jpeg) and this is how it looks now: ![iScreen Shoter - Fibery - 250608181852b](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/8/860f25577e598484619361932bc1e54a25d1bef4.jpeg) and here’s a similar example, with more related entities: ![iScreen Shoter - Fibery - 250608185051](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/37724523cdb90423ccf72de5c51a5bea213a97f3.jpeg) ---
**Author:** ![Renato\_Carvalho](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/renato_carvalho/32/11001_2.png) [@Renato\_Carvalho](https://community.fibery.io/u/Renato_Carvalho)\ **Post date:** [June 9, 2025, 10:04am UTC](https://community.fibery.io/t/how-we-handle-a-view-with-too-many-related-entities/8949/2 "2025-06-09T10:04:46Z")
Really clever! ✨ Thank you for sharing this @Mircea_Braescu ---
**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\ **Post date:** [June 9, 2025, 10:34am UTC](https://community.fibery.io/t/how-we-handle-a-view-with-too-many-related-entities/8949/3 "2025-06-09T10:34:40Z")
This looks lovely!! Nice workaround to make things more organised. Thanks for sharing! Just wondering, is the “system modeling” and “related entities”, new databases? They are then unused, and are just to make prettier naming in the entity view? Lovely workaround! I think this is related to this: [Add a view of "Collection" entities within another entity that are not related, just for reference - #2 by RonMakesSystems](https://community.fibery.io/t/add-a-view-of-collection-entities-within-another-entity-that-are-not-related-just-for-reference/568/2). Then you could just create a view to show all relations, and hide the real relations. Like you did, but with proper naming. Its almost like polymorphic relations if you don’t think about it too hard haha Good stuff! ---
**Author:** ![Mircea\_Braescu](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mircea_braescu/32/9729_2.png) [@Mircea\_Braescu](https://community.fibery.io/u/Mircea_Braescu)\ **Post date:** [June 9, 2025, 1:07pm UTC](https://community.fibery.io/t/how-we-handle-a-view-with-too-many-related-entities/8949/4 "2025-06-09T13:07:34Z")
> [@RonMakesSystems](#): > > Just wondering, is the “system modeling” and “related entities”, new databases? They are then unused, and are just to make prettier naming in the entity view? That’s exactly how it is. I tried some alternatives but this felt like the cleanest approach.