# How we handle a view with too many related entities

**URL:** <https://community.fibery.io/t/how-we-handle-a-view-with-too-many-related-entities/8949>\
**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:** 1\
**Showing post:** 4

<div class="post-metadata">

**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")

</div>

> [@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.

---

_[View the full topic](https://community.fibery.io/t/how-we-handle-a-view-with-too-many-related-entities/8949)._