Skip to content

Conversation

@labkey-susanh
Copy link
Contributor

Rationale

With the fix for Issue 52098, that allows us to resolve number names for lookups more reliably, we are also changing the pre-trigger convert data iterator to throw an error instead of returning the original value if a lookup resolution fails, which means that if supplying an alternate key value the caller needs to indicate that that is happening so the proper kind of lookup resolution can be used. To do this in the test setup, we switch to using the ImportDataCommand instead of InsertRowsCommand.

Related Pull Requests

Changes

  • Update uploadData method in test setup to import from the file and indicate we are supplying alternate keys, except when the responses are needed.

@labkey-susanh labkey-susanh merged commit 5bd2f99 into develop May 26, 2025
5 of 6 checks passed
@labkey-susanh labkey-susanh deleted the fb_lookupResolutionType branch May 26, 2025 13:22
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