Forum Discussion
401 Error when rebinding report
We're doing some preliminary exploration of the API via PowerShell and receiving a 401 error when attempting to rebind a report to a new dataset. Other API calls are successful, including other POST actions like cloning. There are no details provided with the 401.
Can anyone offer any insight as to what may be causing this?
A GET to this URL works fine:
https://api.powerbi.com/v1.0/myorg/groups/$ReportWorkspace/reports/$ReportID
And so does a POST here (necessary parameters passed in the body):
https://api.powerbi.com/v1.0/myorg/groups/$ReportWorkspace/reports/$ReportID/Clone
A POST to this URL results in a 401 (datasetID passed in the body):
https://api.powerbi.com/v1.0/myorg/groups/$ReportWorkspace/reports/$ReportID/Rebind
Having this functionality work is an important part of our planned deployment for PowerBI, and I spent far too long yesterday pounding my head against this vague error. Any direction would be appreciated!
The Rebind API works in my test, as to 401, it is a unauthorized issue, please go to Azure portal and ensure that you've set all permissions for the registered app and then click grant permissions.
2 Replies
The Rebind API works in my test, as to 401, it is a unauthorized issue, please go to Azure portal and ensure that you've set all permissions for the registered app and then click grant permissions.
We've been skating by so far using the ClientID supplied by the PowerShell library we're using - attemping to pass our own ClientID results in errors I've been trying to avoid troubleshooting, but it sounds like it's time for us to put our big boy pants on and do this the right way.
Appreciate the info!
