microsoft / microsoft/vscode-powerquery-sdk
Set credentials fails - referencing multiple data source kinds in same connector
@mattmasson is already working on this.
Since Mar 18, 2024.
- Dominant language
- TypeScript
- Stars
- 92
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
Preflight Checklist
- I have installed the latest version of Power Query SDK.
- I have checked existing resources, including the common issues and the release notes.
- I have searched for similar issues.
Power Query SDK
2.0.0
Regression From
No response
Platform
Windows
Architecture
x64
OS Version
No response
VSCode version
No response
PQSdkTool Path
No response
Bug Description
When a test M file contains references to multiple data source kinds defend by the same connector, setting credentials fails.
Steps to Reproduce
- Create a connector that defines multiple data source kinds:
[Version = "1.0.0"] section BenTest; [DataSource.Kind="BenTest"] shared BenTest.Data = () => ...; [DataSource.Kind="BenTest2"] shared BenTest2.Data = () => ...; BenTest = [ Authentication = [ Anonymous = [] ]]; BenTest2 = [ Authentication = [ Anonymous = [] ]]; - Create a test M file that references more than one of these data source kinds:
section Tests; shared A = BenTest.Data(); shared B = BenTest2.Data(); - Run "set credentials".
Actual Experience
Set credentials process prompts the user to select which data source kind they are setting credentials for and the M test file, as well as the credentials kind (all as expected; good), before erroring with the following (bad):

Expected Experience
Credentials for the specified kind should have been successfully set.
Additional Context
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.