The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
I'm working with PowerBi REST APIs.
While trying to Export a report from the workspace I'm getting
'404 Client Error: Not Found for url: https://api.powerbi.com/v1.0/myorg/groups/my-workspace-id/reports/my-report-id/Export'
If I request https://api.powerbi.com/v1.0/myorg/groups/my-workspace-id/reports then 'my-report-id' is listed in the responce with webUrl: https://app.powerbi.com/groups/my-workspace-id/reports/my-report-id
One more thing to notice, 'my-report-id' is cloned from a different workspace and bound to my-workspace-id's semantic model. The reports created directly inside 'my-workspace-id' get exported but not the one cloned from differnt workspace.
Don't know what is the reason behind this.
Solved! Go to Solution.
Hi @ms_query
Thank you for using Microsoft Community Forum.
When a report is cloned using the API or bound to a semantic model from another workspace, Power BI generates only metadata for the report in that workspace. No PBIX file is created or transferred in this process. This is why the report’s isFromPbix property is set to false.
Because there’s no PBIX file stored behind these reports in the workspace, that is why we are getting 404 error.
If this information is helpful, please “Accept as solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.
Thank you.
Hi @ms_query
I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, please Accept it as a solution and give it a 'Kudos' so others can find it easily.
Thank you.
Hi @ms_query
Thank you for using Microsoft Community Forum.
When a report is cloned using the API or bound to a semantic model from another workspace, Power BI generates only metadata for the report in that workspace. No PBIX file is created or transferred in this process. This is why the report’s isFromPbix property is set to false.
Because there’s no PBIX file stored behind these reports in the workspace, that is why we are getting 404 error.
If this information is helpful, please “Accept as solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.
Thank you.
Hi @ms_query
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.
@v-priyankata Thanks for your inputs, but there is no solution for the problem as Power BI Desktop interaction is not involved.
Hi @ms_query
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
Hi @ms_query
Thank you for reaching out to Microsoft Fabric Community.
please try below steps it may helps you
Thanks @v-priyankata for replying,
This is an odd behaviour which is not documented by Microsoft.
Even though the source report is from pbix file, but during the cross workspace cloning it losses the link to root pbix file and gets created by power-bi service.
And rest/REST is as expected.
Hi @ms_query
Please look into below points.
Thanks @BhavinVyas3003 for the reply,
But it doesn't help. BTW the dataset was already linked when the clone API was triggered.
I notice one more diference, the property 'isFromPbix': False of reports for cross workspace cloning. Don't know why it is changed while the source version has this property True.
The 404 error occurs because the cloned report is still linked to the original dataset or has metadata not fully registered in the new workspace.
To fix this: