Exactly! It’s related to this: Add a view of "Collection" entities within another entity that are not related, just for reference, and this: How we handle a view with too many related entities - #4 by Mircea_Braescu. We right now need to make “fake” relations just to have access to another view in the entity view.
I agree! I think in general this is the required use case, but the only places where you might want a different dashboard layout / views per entity is:
- The dashboard database. Or else every dashboard entity is the same and that defeats the point…
- Maybe the “User” entities. Then each user could set their own dashboard in their user entity.
- Maybe a joker dashboard view on an entity that is specific to that entity, if a project is larger and needs a different dashboard to other projects, etc.
I’m proposing a toggle for “Same dashboard for all [database name]s” or “Unique dashboard per [database name]”
Then you could have multiple entity views even, one thats the same across projects, and one that’s project specific. Maybe!
One question is permissioning. I would argue that when a dashboard is different per entity, anyone with edit access to the entity can configure the dashboard, and when the dashboard is the same across entities, only creators can edit. Similar to the way a formula field works vs a text field. Formulas are the same across the db, so only creators can configure, text fields are per entity, so anyone with edit access can edit. Not 100% sure about this one though!