microsoft / microsoft/powerbi-powershell

RDL file import in API is broken in several ways

Open
#218 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
413
Forks
134
Avg merge
33m
Merged PRs (30d)
1

Description

Trying to automate RDL file upload using Invoke-PowerBIRestMethod and the /groups/<group>/imports POST endpoint seems borderline impossible currently - there are several problems:

  • No examples online - every example uses Invoke-RestMethod (none of which work)

  • Content-Type header parsing is broken, for example "multipart/form-data; boundary=someboundary" (with or without quotes around the boundary) results in an error saying that the header value is invalid. Same header works in Invoke-RestMethod. This makes it impossible to send multipart data as the boundary can't be specified.

  • Every single permutation of trying to do an RDL import returns 400 with no other information and the documentation/Swagger doc doesn't really help. e.g do we need to supply datasetDisplayName with RDL even though there is no seperable dataset?

Any example of importing an RDL would be useful - I haven't found any at all using Invoke-PowerBIRestMethod and haven't found any with other cmdlets that work.

Contributor guide

Open the contributing guide

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 with the Invoke-PowerBIRestMethod cmdlet and the /groups//imports POST endpoint described in the issue. Reproduce the multipart/form-data boundary error and the 400 response for an RDL import; done means identifying working import parameters and providing an example or resolving the reported request handling problems.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
api, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.