When creating a new field in a database, the new field appears in ALL Entity Views (all tabs).
As a result, I need to remove the field from all Entity Views except from the one I want the field to show.
I think that as good as nobody will need a new field to appear in all Entity Views. At least I never encountered that need.
Removing the new field from all Entity Views is a lot of work each time.
Related:
Also, when creating a new Entity View, it includes ALL fields. That is a lot of work to remove the fields, since the purpose of an Entity View is to focus on a clean view. Although a workaround is to clone an existing Entity View, it is not intuitive and I often end up deleting new Entity Views in order to clone an existing one.
So, the expected/desired behavior would be:
When Adding a new Entity View, do not populate it with any fields (or only with the default Entity View fields)
When creating a new field, do not include it in every Entity View.
I find it very counter-intuitive that a field I create somewhere just pops up in all entity views..
Usually you create an entity view with a specific purpose. If I want to edit an entity view, I will do just that. Just because I created a new field it doesn’t mean it belongs to all entity views.
In my opinion default behavior should always be to enable the field only in the view where it was created.
I noticed this happening far more often now that I’m creating more complex reports and and connections especially with AI via MCP. Because there are often a bunch of helper fields created for the purpose of the report/view and then have to go through every View and remove the newly created fields
If I’m in UI and add a field from the View itself, then yes visible. Otherwise not visible on any other view I would need to enable it on each view