Forum Discussion
404 Client Error - Export Report In Group
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.
- Open the original report in Power BI Desktop and Publish it to your target workspace. that ensures the service has a true PBIX.
- If you need a PBIX file to export, open the report in the Power BI Service, go to File > Download this file (PBIX), save it to your computer, and then re-publish it to the workspace. This will create a proper PBIX file in the workspace that you can then export.
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.- Open the original report in Power BI Desktop and Publish it to your target workspace. that ensures the service has a true PBIX.
Hi ms_query
Thank you for reaching out to Microsoft Fabric Community.
please try below steps it may helps you
- The report you’re trying to export was cloned from another workspace, and it has a property called 'isFromPbix': False. That means it wasn’t uploaded from a .pbix file, and reports like that usually can’t be exported using the REST API—even if they show up fine and are connected to the right dataset.
- For the export API to work, the report needs to have been originally uploaded as a .pbix file into the workspace. Cloning from another workspace won’t work here.
- The fix is to re-upload the original .pbix file directly into the workspace instead of cloning it. Once it’s uploaded properly, the report should be exportable.
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.
Thanks Anonymous 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.- Re-upload or Re-publish the report in the target workspace.
- Download the .pbix of the cloned report.
- Open it in Power BI Desktop.
- Re-bind it to the dataset in my-workspace-id (if not already).
- Re-publish it to the same workspace.
- Try the export API again.
- Check for Dataset Binding
- Use the Get Report In Group API to confirm that the report is correctly bound to the dataset in my-workspace-id.
- Export API Permissions
- Ensure your service principal or user has Report.ReadWrite.All permission AND access to both:
- The workspace (my-workspace-id)
- The report (especially if it’s cloned — permissions don’t always carry over properly)
- datasetId matches a dataset in the same workspace
- reportType is PowerBIReport
- You’re not seeing fields like isFromPbix = false (which might indicate cloning)
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.
