# Fields applicable to all types **URL:** \ **Category:** Ideas & Features\ **Tags:** flexible-domain\ **Created:** [August 24, 2020, 2:06pm UTC](https://community.fibery.io/t/fields-applicable-to-all-types/910 "2020-08-24T14:06:02Z")\ **Posts on this page:** 1\ **Showing post:** 10
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [August 30, 2020, 11:33pm UTC](https://community.fibery.io/t/fields-applicable-to-all-types/910/10 "2020-08-30T23:33:09Z")
> [@B\_Sp](#): > > I often have within a Type one particular Entity that I want to relate to a whole other “child” Type. One example is in my Software Platform, I have one entire component, which is a Type as there are many components, which relates to another Type in another App. So I don’t really want that “child” Type In the other App to relate to every other of the Component “parent” type, but I have to right now. This also means that in the App “Map” feature (I’m talking about the visual that you get with connectors across your apps at the bottom left of Fibery, which in and of itself is a great feature unique to Fibery!), I will see this one “child” Type related to the entirety Component “parent” Type. One of the challenges of developing a system like Fibery (or indeed Notion and other similar things) is that there _can_ be many ways of doing something and, before they are implemented, there are many ways to even conceive of accomplishing the goals of some group of users. What you’re suggesting here would _seem_ to map fairly well to the way I see embedded Views working: > [@\[DONE\] Embed Custom Views into Entity View](https://community.fibery.io/t/embed-views-in-rich-text/936): > > This has been mentioned several times in various posts and requests, but never really seemed to have its own clear feature request, and I think it’s important: We need the ability to embed arbitrary Views into Rich Text fields anywhere (including Documents). Notion is really the best existing example of this and for the most part it handles this very well. You can embed a view of a database (Type) and filter and sort it as you desire. You can change the view type, card, calendar, list, gallery.… In particular, and as an extension to that idea, if there were a way to (optionally?) show a “loose” or “ad-hoc” relationship between an Entity and any View that embedded it (this could just be in the existing References section, but it might be beneficial to have it separated out, I’m not sure). Looking at the above feature request, would it address your need here, and if not, what is it lacking? I ask because I think embeddable views are an extremely flexible way to solve a variety of challenges, including (potentially) this one. Whereas I don’t see a clean and obvious solution to what you’re suggesting. Although… OK, I just had another thought. Which is a pretty radical change to how Fibery works, so probably not likely to be implemented. But… What if we had a “switch” (toggle) at the top of the Entity view that toggled between edit or “linking” mode, and view/reference mode. In Edit/Linking mode you’d see every field, relationship, etc. regardless of whether there was anything in it. While in view/reference mode you’d only see fields that had data, including relations. And perhaps you could control globally for _your_ user account whether entities defaulted to View or Edit mode. Hmm… Like I said, it’s a radical change, but I’m curious if there is any nugget of value in it. It’s a simple-seeming thing that could actually help address a number of other challenges outlined here in the forums… @mdubakov any thoughts? --- _[View the full topic](https://community.fibery.io/t/fields-applicable-to-all-types/910)._