microsoft / microsoft/powerbi-powershell
Get Refresh History In Group, optional parameter {$top} not functional.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 413
- Forks
- 134
- Avg merge
- 33m
- Merged PRs (30d)
- 1
Description
Expected behaviour:
GET https://api.powerbi.com/v1.0/myorg/groups/{groupId}/datasets/{datasetId}/refreshes?$top={$top} should only return {$top} amount of entry.
e.g GET https://api.powerbi.com/v1.0/myorg/groups/f089354e-8366-4e18-aea3-4cb4a3a50b48/datasets/cfafbeb1-8037-4d0c-896e-a46fb27ff229/refreshes?$top=1 (from official documentation) I should expect only one entry in the response.
Current behaviour:
For me, changing the {$top} parameter makes no changes to the response. No matter what {$top} is, I always get the same amount of entries in my response.
How to replicate:
Use the above API call on any datasets with multiple refresh entries, and see the parameter {$top} makes no changes to the response.
Side note:
It's not a big issue as I can chop up the response myself, however, this might still be a bug in the API.
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 by reproducing the documented GET refreshes endpoint on a dataset with multiple refresh entries, varying the $top value and comparing response counts. Determine whether the parameter is lost by the PowerShell module or ignored by the Power BI API; done means documenting the confirmed cause and an appropriate fix or escalation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100