Issue 53536: LKSM/LKB: Moving assay runs with multiple file fields may populate file fields incorrectly#6881
Merged
XingY merged 1 commit intorelease25.7-SNAPSHOTfrom Jul 30, 2025
Merged
Conversation
…y populate file fields incorrectly
labkey-susanh
approved these changes
Jul 29, 2025
Contributor
|
Code change makes sense given that we don't allow you to move a run if a file is referenced by more than one field. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rationale
Issue 53536: LKSM/LKB: Moving assay runs with multiple file fields may populate file fields incorrectly
The related PR introduced a bug that sets a file field value even though there is no relevant file values found for that field.
Related Pull Requests
Changes
Tasks 📍