Overview
When working with Labsheets inside Labspace (experiment/protocol) pages, not all data is always relevant to the task at hand. By default, embedded Labsheets display all columns, which can make the interface cluttered and harder to use.
With View-based embedding, you can now select a specific saved View (such as QC View) when embedding a Labsheet. This ensures that only the most relevant columns, filters, and structure are shown.
This helps:
Reduce visual clutter
Improve focus during workflows
Prevent editing of irrelevant fields
Maintain consistency across teams
What This Feature Does
When embedding a Labsheet into a Labspace (experiment/protocol) page, you can now:
Select from existing saved Views
Embed only the columns defined in that View
Preserve column order, filters, and permissions
Ensure consistency across all users viewing the page
If no View is selected, the Labsheet will default to the standard behavior (showing all columns).
How It Works
1. Open the “Add Labsheet” Flow
From within your Labspace (experiment/protocol) page:
Click to add or embed a Labsheet
Select the Labsheet you want to embed
2. Select a View
In the embed dialogue:
You will see a View selector dropdown
Choose from any saved Views (e.g., Master View, QC View)
Default behavior:
If a default View is set → it appears first
If no default View is set → Master View is selected
3. Embed the Labsheet
Once embedded:
Only the columns defined in the selected View are shown
Hidden columns are not visible or editable
The layout reflects the chosen View exactly
Behavior Across Users and Pages
Shared View State
The selected View is tied to the page/template, not the individual user.
If User A selects QC View → all users see QC View
If User B changes it → it updates for everyone
Per-Page Configuration
Each embedded Lab Sheet is independent:
The same Lab Sheet can be embedded in multiple pages
Each page can use a different View
Changes in one page do not affect others
Live View Updates
If a saved View is updated:
All embedded Lab Sheets using that View will automatically reflect the changes
Permissions and Data Control
Users cannot see or edit columns that are not part of the selected View
Permissions defined in the View are enforced in the embedded table
This helps maintain data integrity and restrict unnecessary edits
Activity Tracking
All relevant actions are logged, including:
Embedding a Lab Sheet with a selected View
Changing the View after embedding
Updates to the embedded configuration
PDF Export Behavior
When generating a PDF-ready document:
The embedded Labsheet reflects the selected View
Not the Master View
This ensures exported documents match what users see in the page.
Why Use View-Based Embedding?
This feature helps teams:
Focus only on relevant data during experiments
Reduce errors from editing unnecessary fields
Standardize how data is presented across workflows
Improve readability in dense Lab Sheets
Key Takeaways
You can now embed Labsheets using specific saved Views
Only selected columns, filters, and permissions are applied
Views are shared across users but scoped per page
Updates to Views propagate automatically
Embedded views are reflected in exports and logs