microsoft / microsoft/vscode-powerquery-sdk

Documentation: Get started

Open
#341 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
92
Forks
23
PR merge metrics
No merged PRs in 30d

Description

Preflight Checklist
Problem

A "Hello World" or Get started guide is missing. What can a user do after this extension was added to vs code?

I assume it helps to create a connector to retrieve records from a datasource (for example a json file) and turn the records into usable output for power bi. But this is not mentioned directly.

Desired Solution

A tutorial that guides the user to create a custom connector using a local json file as input and convert this into output (tables) suited for Power BI Desktop

Alternatives and Workarounds

There is no alternative for a getting started guide

Additional Context

In my use case i want to use the jira rest api to get issue data in a json file (multiple nested json objects). I want to import these into Power BI to create some report (bugs created by week / month) bugs solved by week / month. Breakdown of created, solved bugs by severity (minor, major, blocker, critical).
The first part to get the data records from a json file and turn the data into a format for power bi by creating a custom connector would be immensly helpfull.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked Power Query SDK release notes and common issues to understand the current extension workflow. Define the tutorial around creating a custom connector from a local JSON file and producing Power BI-compatible tables. Done means a newcomer can follow the guide from extension installation through usable output.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.