Skip to content

GitHub Issue 563: Assay results default view to include Run/Name #7260

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
cnathe merged 2 commits into from
Dec 15, 2025
Merged

GitHub Issue 563: Assay results default view to include Run/Name #7260

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ae47b49
GitHub Issue 563: Assay results default view to include Run/Name
cnathe Dec 12, 2025
7999328
Merge branch 'develop' into fb_workflowAssay563
cnathe Dec 15, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions assay/api-src/org/labkey/api/assay/AssayResultTable.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -244,6 +244,7 @@ else if (baseColumn.isMvIndicatorColumn())
for (FieldKey calculatedFieldKey : calculatedFieldKeys)
visibleColumns.add(FieldKey.fromParts("Run", calculatedFieldKey.getName()));
}
visibleColumns.add(FieldKey.fromParts("Run", "Name"));
Copy link
Contributor Author

@cnathe cnathe Dec 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@labkey-klum Do you see any issue with adding this to the default view for Assay results/data grids? We already add the run properties to the default view, we just have never added the run Assay ID / Name column.

Copy link
Contributor

@labkey-klum labkey-klum Dec 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think it would hurt anything. The existing set of default columns seems mostly arbitrary.


for (DomainProperty prop : _provider.getBatchDomain(_protocol).getProperties())
{
Expand Down