Update test to use ImportData when importing with alternate keys #826
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
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
ImportDataCommandinstead ofInsertRowsCommand.Related Pull Requests
Changes
uploadDatamethod in test setup to import from the file and indicate we are supplying alternate keys, except when the responses are needed.