microsoft / microsoft/powerbi-powershell
Get-PowerBIReport: Specifying -WorkspaceId breaks WebUrl & EmbedUrl properties on Paginated Reports
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 413
- Forks
- 134
- Avg merge
- 33m
- Merged PRs (30d)
- 1
Description
Example:
Get-PowerBIReport -Scope Organization | Where-Object -Property Name -EQ "My Paginated Report"
Returns:
Id : XXXXXXXXXXX
Name : My Paginated Report
WebUrl : https://app.powerbi.com/rdlreports/XXXXXXXXXXX
EmbedUrl : https://app.powerbi.com/rdlEmbed?reportId=XXXXXXXXXXX&otherparams
DatasetId :
But, when you specify the workspace that report is in like this:
Get-PowerBIReport -Scope Organization -WorkspaceId XXXXXXXXXXX | Where-Object -Property Name -EQ "My Paginated Report"
It returns this:
Id : XXXXXXXXXXX
Name : My Paginated Report
WebUrl : https://app.powerbi.com/groups/YYYYYYYYYYY/reports/XXXXXXXXXXX
EmbedUrl : https://app.powerbi.com/reportEmbed?reportId=XXXXXXXXXXX&groupId=YYYYYYYYYYY&otherparams
DatasetId :
The URLs in the second example are wrong, unless you replace "reports" with "rdlreports" and "reportEmbed" with "rdlEmbed".
If I was just using the URLs, I would do simple regex string replacement... Sadly, what I'm actually trying to do is retrieve a list of ONLY the standard Power BI reports (NOT paginated), but since the URL is the only property that seems to offer a way to distinguish between Power BI and Paginated reports returned by this command, I can't tell them apart when I use the WorkspaceId parameter.
Contributor guide
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
Start at the Get-PowerBIReport entry point and compare its behavior with and without -WorkspaceId for paginated reports. Done means the returned WebUrl and EmbedUrl identify paginated reports correctly in both cases, allowing standard and paginated reports to be distinguished without string replacement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100