Views and presentation
Views and presentation shape how you read Records & Lists. Save a useful display when you want to return to it without changing the Records.
Ownership
Views and presentation retain a display's filters, sort, columns, and layout. A saved View belongs to its registered table context. A personal View is visible to its creator. A team View is shared within its allowed scope. A View does not own the values it displays. Reading a shared View still applies the caller's access to the underlying Records and fields.
Lifecycle
Views and presentation keep saved configuration apart from each member's active choices. View pins retain which saved Views appear as tabs and their order for that member. The Console's Pinned group beside Lists holds personal List shortcuts. Removing a pin removes a shortcut, not the saved View, List, or its members. Another member can therefore keep a different set of shortcuts to the same work.
Boundaries
Views and presentation use the modes the current context can render. A List route opens its member table. An unknown view mode falls back to that table. The board control stays disabled on a List route. A link requesting the board does not render one. A List route resolves to the List itself, while the board requires a target naming one Entity kind.
Failures
Views and presentation cannot make a stale field or unsupported layout valid. Saved View authoring checks the registered table context. A field change can make an old display unsuitable. A missing personal View may also belong to a different signed-in member. Changing the display cannot repair missing membership or grant access to masked values. Inspect the underlying List or Record when the data, rather than its display, is wrong.
Recovery
Views and presentation are best repaired from the current table. Find the List through lists.list, check its members, and use the supported table mode. Revise filters or columns against the current fields before saving the display. Re-pin an accessible View when only its tab is missing. If the List itself is wrong, Lists and membership explains the target and membership controls.
Related
- Lists and membership helps operators distinguish a missing member from a filtered display.
- Records and history explains current and past values when the underlying data needs inspection.
- Import and target records builds a shared work target before choosing its presentation.