# New view: relationships map **URL:** \ **Category:** Ideas & Features\ **Created:** [August 27, 2024, 12:43pm UTC](https://community.fibery.io/t/new-view-relationships-map/6556 "2024-08-27T12:43:05Z")\ **Posts on this page:** 12\ **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:** [August 27, 2024, 12:43pm UTC](https://community.fibery.io/t/new-view-relationships-map/6556/1 "2024-08-27T12:43:05Z")
Atlassian had this tool called Compass which had an interesting feature: a dependency map which allowed you to explore a graph by going from node to node. I think something like this would be a great addition to Fibery. ![Dependency map (1)](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/c/c25edaf4d407e6cd54a78ad7ba94354468185f6e.gif) > **[Idea: Visual dependency map](https://community.atlassian.com/t5/Compass-articles/Idea-Visual-dependency-map/ba-p/1882618)** > > Hi everyone, Ra here from the Compass design team. I would like to share a visual dependency map concept we recently explored during innovation week. Currently, we have a dependency list view where you can see the upstream and downstream dependencies... ---
**Author:** ![lerone](https://avatars.discourse-cdn.com/v4/letter/l/cab0a1/32.png) [@lerone](https://community.fibery.io/u/lerone)\ **Post date:** [August 27, 2024, 1:10pm UTC](https://community.fibery.io/t/new-view-relationships-map/6556/2 "2024-08-27T13:10:38Z")
it´s great! I have also seen this coming up in other high-level knowledge navigation apps. the really nice thing about it: it allows for navigating _heterogenous_ pathways, seamlessly _connecting different (entity) types_! – … this pretty much relates to the whole aspect of ‘complex model spaces’ / ‘concept maps’ that is part of this whiteboard discussion, IMO. 👉 [Whiteboard as context (= information) – how to use this 'insight' in Fibery? - #15 by lerone](https://community.fibery.io/t/whiteboard-as-context-information-how-to-use-this-insight-in-fibery/6536/15) ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [August 27, 2024, 1:11pm UTC](https://community.fibery.io/t/new-view-relationships-map/6556/3 "2024-08-27T13:11:21Z")
Have you tried the experimental feature for showing entity collections? > [@August 14, 2024 / robot Manage automation Rules as a Creator, New sidebar design, Expand cards to show nested collections](https://community.fibery.io/t/august-14-2024-manage-automation-rules-as-a-creator-new-sidebar-design-expand-cards-to-show-nested-collections/6504): > > Tomorrow is a holiday in Poland and Cyprus, so we are releasing today. This release has at least one long-awaited feature, sprinkled by some less expected things. Enjoy! robot Manage automation Rules as a Creator (special for Shlomi, Rob, and 40 more people) No more 12 Admins in a workspace, no more “could you please set up this Rule for me”. Now everyone with Creator access to a Space can configure no-code automation Rules and Buttons. Since you can traverse relations beyond the … ---
**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:** [August 27, 2024, 3:58pm UTC](https://community.fibery.io/t/new-view-relationships-map/6556/4 "2024-08-27T15:58:57Z")
I haven’t tried it but I saw the video, and it’s a somewhat different use case imo ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [August 27, 2024, 4:11pm UTC](https://community.fibery.io/t/new-view-relationships-map/6556/5 "2024-08-27T16:11:08Z")
Please try it and let us know what the missing features are 🙂 ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [August 28, 2024, 5:54am UTC](https://community.fibery.io/t/new-view-relationships-map/6556/6 "2024-08-28T05:54:14Z")
> [@Mircea\_Braescu](#): > > I haven’t tried it but I saw the video, and it’s a somewhat different use case imo It is exactly the same use case as I see it ---
**Author:** ![lerone](https://avatars.discourse-cdn.com/v4/letter/l/cab0a1/32.png) [@lerone](https://community.fibery.io/u/lerone)\ **Post date:** [August 28, 2024, 8:39am UTC](https://community.fibery.io/t/new-view-relationships-map/6556/7 "2024-08-28T08:39:17Z")
hey there, I tested it, and generally the multi-entity insert is a great function, especially given it´s flexibility around filtering etc! 🚀 From comparing the 2 experiences + my knowledge of similar functions in other tools, I´d say one can go very far with this. There remains a (closable) gap between the 2 use cases / experiences of _building an (explorational) view_ and _navigating_, I would think. With navigation – like in the so-named ‘Compass’ – being automatic and instant, that is easily navigable. While the current experinmental feature needs clicking and decisioning, and produces a stable _view_, not a dynamica one, like the Atlassian… 🧭 The OP (@Mircea_Braescu ) would of course have to say whether this was on his / her mind; but that is where I feel the difference currently. 🫰 Plus, I deliberately wrote ‘(closable) gap’ bec I think there is an easy way to reconcile both modalities (exploration & building view vs. dynamic, instant navigation) and get to a hybrid: if the last toggle, showing the selectable collections, would give a hover preview of all the titles of the entity set, it would potentially change the experience ‘dramatically’, in terms of giving that feel of contextual, ad-hoc navigation. 🤔 (It would be even more so, if all the hovers over context menus would open the modals… but that is not a vote for that… 🙃) ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [August 28, 2024, 8:43am UTC](https://community.fibery.io/t/new-view-relationships-map/6556/8 "2024-08-28T08:43:13Z")
In Fibery there are situations when you have dozens of collections with thousands entities, so no simple solutions will work. What we implemented is the only one we found can work for many collections and many entities. If you can invent a better approach, we’d be happy to hear it ---
**Author:** ![lerone](https://avatars.discourse-cdn.com/v4/letter/l/cab0a1/32.png) [@lerone](https://community.fibery.io/u/lerone)\ **Post date:** [August 28, 2024, 9:13am UTC](https://community.fibery.io/t/new-view-relationships-map/6556/9 "2024-08-28T09:13:30Z")
ok, sorry. I can´t contribute more than some constructive ‘thinking along’ as a proficient & interested simple user; and the idea of navigation vs. view building (for differentiating use cases). and the proposal / idea I already gave (hover preview). 🌻 ---
**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:** [August 28, 2024, 2:38pm UTC](https://community.fibery.io/t/new-view-relationships-map/6556/10 "2024-08-28T14:38:28Z")
> you have dozens of collections with thousands entities Yes, but any single entity will usually only be connected to a few other entities, probably not more than a dozen or so, and the benefit with the suggested approach is that it would be a quick and non-overwhelming approach to navigate and visualize what could otherwise be spaghetti (a big graph / network) ![shot_240828_173640](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/9/95c9d8ea033584a1544ea2fba74459e56b66b31f.png) ---
**Author:** ![njyo](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/njyo/32/923_2.png) [@njyo](https://community.fibery.io/u/njyo)\ **Post date:** [August 28, 2024, 3:55pm UTC](https://community.fibery.io/t/new-view-relationships-map/6556/11 "2024-08-28T15:55:06Z")
Actually, in our Fibery setup we use connections heavily. And while the classic 7±2 rule applies, for connections of one type, we have entities connect to many other types. One example would be a `UI Component` entity, it’ll connect to: 1. Child/parent components 2. Business Object Entity 3. Screen/Page 4. Copy Strings and Errors 5. Features/Actions that they trigger So together these will amount to a good amount of connections that I may want to see or not. And other key nodes will have similar number of connections. It’s not an unsurmountable problem and I’ve actually made a PoC in a completely different space that solved that problem, but it’s not trivial. And it’s pretty much in line with what the team has implemented with the ability to unfurl and show/hide edges based on type. ---
**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:** [August 28, 2024, 5:06pm UTC](https://community.fibery.io/t/new-view-relationships-map/6556/12 "2024-08-28T17:06:00Z")
> Please try it and let us know what the missing features are I tried it and it’s exactly what it showed in the video. A powerful way to add related entities to an whiteboard, and I’m sure we’ll make use of it in some cases, but it’s not a tool I would to navigate through the graph of relationships. With a view like the one in compass I can get to a 3rd degree removed dependency in 3 clicks. The closest approximation of that in Fibery would be the entity details view. I see the related entities for an item and I click one of them… Then I see the details and related entities of that item and click another one … and so on and so forth.