# Merge or “Consolidate” Extended Relations in Collection Views and Boards

**URL:** <https://community.fibery.io/t/merge-or-consolidate-extended-relations-in-collection-views-and-boards/1178>\
**Category:** Ideas & Features\
**Created:** [November 16, 2020, 6:16pm UTC](https://community.fibery.io/t/merge-or-consolidate-extended-relations-in-collection-views-and-boards/1178 "2020-11-16T18:16:34Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**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:** [May 20, 2025, 10:33pm UTC](https://community.fibery.io/t/merge-or-consolidate-extended-relations-in-collection-views-and-boards/1178/12 "2025-05-20T22:33:28Z")

</div>

@B_Sp I see two things here.

1. Show the data (from same databases) accross different context filters in one view.

> [@B\_Sp](#):
>
> So I think it would be great if we could consolidate when we create extended connections to the same Type, without having multiple Collections that are in isolation from each other, even though they are about the same Type.

This sounds very similar to this, no? [Show several context filters at the same time](https://community.fibery.io/t/show-several-context-filters-at-the-same-time/8503)

The thing is this its only on a view level and not on a data level. So board view grouped by different fields of common type wouldn’t be possible. But I dont quite understand the use case here. Here’s what I’m thinking: [https://youtu.be/hYoshHmoQBM](https://youtu.be/hYoshHmoQBM)

1. 

Merge different lookups from different databases into one view.

This one i don’t really understand. I’m not sure if i got it correctly… Whats the use case here? Why is it needed?

Curious to hear your thoughts.

---

_[View the full topic](https://community.fibery.io/t/merge-or-consolidate-extended-relations-in-collection-views-and-boards/1178)._