Skip to content

Conversation

@labkey-susanh
Copy link
Contributor

@labkey-susanh labkey-susanh commented Jan 19, 2026

Rationale

Issue 436 The logic for resolving file links field data allows for the possibility of users providing the rowId for the file in the exp.data table, which is something that may (or may not) be relied upon for assay data import. If a user happens to name a file with just a number (123) and that number happens to coincide with a rowId in the exp.data table, the incorrect file will be chosen to associate with that File field. Since we don't believe anyone importing or updating sample file fields will rely on the ability to resolve by RowId, we make a change here to skip that conversion logic for sample file fields.

Related Pull Requests

Changes

  • Add variant of ExpDataFielConverter.convert that take a parameter indicating if resolution by RowId should be tried.
  • Call the new variant from ExpDataIterators::FileLinkDataIterator

@labkey-susanh labkey-susanh requested a review from cnathe January 19, 2026 17:08
@labkey-susanh labkey-susanh changed the title Stop trying to resolve sample file fields by RowId Issue 436: Stop trying to resolve sample file fields by RowId Jan 19, 2026
@labkey-susanh labkey-susanh merged commit cd3fc09 into develop Jan 20, 2026
6 checks passed
@labkey-susanh labkey-susanh deleted the fb_rowIdFiles branch January 20, 2026 00:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants