Explore and share Fabric Notebooks to boost Power BI insights in the new community notebooks gallery.
Check it out now!Microsoft is giving away 50,000 FREE Microsoft Certification exam vouchers. Get Fabric certified for FREE! Learn more
Hello fellow Data Nuts 😁
I decided to dip my toe in the mystical world of the PowerBI REST API today and while I am up and running I am facing an issue where I am getting an error when I am trying to use the "Update Report Content" API Call.
{
"error": {
"code": "PowerBIEntityNotFound",
"pbi.error": {
"code": "PowerBIEntityNotFound",
"parameters": {},
"details": [],
"exceptionCulprit": 1
}
}
}
POST https://api.powerbi.com/v1.0/myorg/groups/{groupId}/reports/{reportId}/UpdateReportContent
{
"sourceReport": {
"sourceReportId": "{sourceReportId}",
"sourceWorkspaceId": "{sourceWorkspaceId}"
},
"sourceType": "ExistingReport"
}
I have a valid bearer token, and other API calls are working fine. I am copying the group and report guid's direct from the URL's in the service but still getting the error message above.
Also, i do have the app setup correctly with all azure app settings, definitely has the correct scope for the call.
Hoping somebody could help me troubleshoot this api call.
Thanks in advance,
David
Solved! Go to Solution.
I wanted to come back here with a clever reason why it was not working, but quite simply because I had made a very very simple rookie mistake. I had my report ID & workspace ID's in the wrong order in the body!
Lesson learned: Triple check your bloody code 🙂
Do you get the same error in the API sandbox?
Reports - Update Report Content In Group - REST API (Power BI Power BI REST APIs) | Microsoft Docs
@lbendlin Unfortunately yes I do. I've deleted report copies in the target workspace, recopied and attempted the report update api call again with the same result.
Then you have bigger issues. Maybe you don't have permission. What's the error in the sandbox?
I wanted to come back here with a clever reason why it was not working, but quite simply because I had made a very very simple rookie mistake. I had my report ID & workspace ID's in the wrong order in the body!
Lesson learned: Triple check your bloody code 🙂