A small idea : an option on fields to hide them for non architects and also an option to hide views on entity.
As architects, sometimes we create intermediate fields to calculate something, to keep a value based on different criteria’s or to simplify formulas by deporting a function on another formula field. And the idea is that this kind of fields :
are hidden by default when we create a new view (and not visible for non architects). So we do not need to hide them manually (Table, List, Board, etc…).
are hidden on entity window.
Imagine that a DB contains some “system” fields. If you want to debug or develop something, it would be great to be able to create an hidden view tab on entity with all the “system” fields.
Interestingly, we are discussing exactly this internally now So far the idea is to add something we call Fields Group to database setup and it will be possible to add fields to different Fields Groups. Then on UI we can create rules to hide all fields for some Groups for some conditions.
In your specific case you also want to hide them by default, so it will be needed to add some kind of special attribute to Field Group to always have it…
I think that new fields should not show on entity views by default. The more sophisticated a database gets the more hidden fields that will exist. Especially now that there are multiple views. The number of hidden fields usually dwarfs the shown fields.
The one exception that I would make to this is if a field is being added directly to an entity view it should show by default to that view only.
Just a quick note to say that if you create a new field from within a specific entity view, it will be hidden by default in the others. So if you want to save time, create in one entity view, hide it there, and you’re done.
True, but if you have two databases with 10 entity views each and now you want to relate them. You’re going to need to go in and hide view by view for at least one of those databases.
+1 here. Or make it a setting per database / per entity view. Or the original request of this topic also solves it
So far the idea is to add something we call Fields Group to database setup and it will be possible to add fields to different Fields Groups. Then on UI we can create rules to hide all fields for some Groups for some conditions.
