microsoft / microsoft/vscode-powerquery-sdk
Function errors at compiling and variable scoping runtime
Nobody has claimed this yet.
- 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
0.4.0
Regression From
No response
Platform
Windows
Architecture
x64
OS Version
Windows 11
VSCode version
1.88.1
PQSdkTool Path
No response
Bug Description
- I'm developing , building and deploy a connector for OpenSearch in PowerBi. When I try to access to the information of a JSON file with
file = File.Contents(<path>),it gives me an error:
Microsoft.Mashup.Engine.Interface.UnpermittedResourceAccessException
The command is tested as inline command from another user Help-request and so, without SDK, work.
- Also, a global variable (declared outside any other object or functions) is read-accessible from other objects or function but not writable even though the IDE mark the variable as [section-member] and assigning a valid value.
Steps to Reproduce
1.Launch Visual Studio Code 2. Compile the project 3. Transfer the .mez file to to proper PowerBI folder 4. Run PowerBI and test
Actual Experience
- It does not complete the compiling.
- Runtime byzantine error as the variable is not modified.
Expected Experience
- Compile.
- The value of the variable should change with a new value assigned.
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.
Research direction
Reproduce both reports with Power Query SDK 0.4.0 on Windows 11 in VS Code 1.88.1, following the listed compile, deployment, and Power BI steps. Investigate the local JSON access failure and the global variable assignment behavior separately; done means the connector compiles and the assigned variable value changes at runtime.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100