Describe the bug
The signature for ExecuteSingleResourceQueryAsync was changed on PR #607 by adding an additional parameter tableName in the middle of other parameters. This change broke tools that were passing other values in the place that this new parameter is using.
Fix
To fix this, we just have to specify the parameter name we're using on all the references.
Known Impact:
Expected behavior
The query sent to the request should be valid.
Actual behavior
Bad request error
Reproduction Steps
Run the Live Tests
Environment
No response
Describe the bug
The signature for
ExecuteSingleResourceQueryAsyncwas changed on PR #607 by adding an additional parametertableNamein the middle of other parameters. This change broke tools that were passing other values in the place that this new parameter is using.Fix
To fix this, we just have to specify the parameter name we're using on all the references.
Known Impact:
Expected behavior
The query sent to the request should be valid.
Actual behavior
Bad request error
Reproduction Steps
Run the Live Tests
Environment
No response