Bases becomes much more powerful when the same underlying data can be surfaced in context-appropriate ways across different notes — a project note showing a Kanban board, a dashboard note showing a Table, etc. Per-embed view pinning would unlock that without requiring file duplication.
Use case or problem
I have a single .base file embedded in two different notes. In each note, I want the base to open with a different default view — for example, a Table layout in one note and a Board layout in another.
Currently, view state is stored in the .base file itself as shared state, so whichever view was last active is what shows up in every embed. There’s no way to tell a specific embed which view it should default to.
Proposed solution
Allow an embedded base to specify which named view it should open with by default, independently of other embeds of the same file. This could work similarly to how you can pass parameters to embeds, for example:
![[mybase.base|view:Board]]
or through a dedicated embed option in the UI.
Current workaround (optional)
Duplicate the .base file and configure each copy separately. This works but breaks the point of reusing a single source of truth for the data.
