Embedded Report: Executing the Query for the Export Data operation resulted in an error.

[fsinclair]

Hi.

I have a dashboard, in which the data source is a web url which links to an excel sheet on an internal SPO page (i did not use the SharePoint Data option when i linked this data, don't ask me why, i followed an online tutorial and the man said it was best). My dashboard is subsequently embedded onto a SharePoint page. I understand powerquery would not work here, but my users have been making do by doing the appropriate filters, and then using the three dots ona table visual, and exporting the data from there. This was working fine up until 2 weeks ago. 

Now, I get the error: Executing the Query for the Export Data operation resulted in an error. 

This error happens within the dasboard in powerbi service, and on the embedded visual on SPO. 

I have tried:

Updating my powerbi app

Refreshing my data

Completely re-adding and reconnecting my data to all the visuals

re-embedding the SharePoint visual

I am an admin for this workspace, so it shouldn't be permissions realted (especially as I am the only admin, and this was working fine up until it wasn't). 

This is an import model. However, this was working, and now I can't do even filter at all without the export failing. There is only a total of 7000 rows in the entire spreadsheet, so the export limit does not apply. 

[fsinclair]

Hi @v-tejrama 

Thank you for your reply. Unfortunate to hear this is a chronic bug. 

Also unfortunately, I get the same error when exporting from the desktop app, and in Power BI service.

[v-tejrama]

Hi @fsinclair ,

Thank you for reviewing this issue across Desktop, Service, and SharePoint. Since the error occurs in all environments, it appears to be related to the export query rather than an embedding limitation.

Export queries can become complex, especially with calculated columns, measures, relationships, or filters. To help isolate the issue, please try exporting a simple table without filters. In Desktop, enabling Performance Analyzer can help identify if a specific calculation is causing the error.

Given that your data source is an Excel file on SharePoint accessed via a web link, certain Power Query transformations such as renaming columns, changing data types, or merging tables may be contributing to the problem. Testing an export from a basic table with raw columns and no transformations or measures can help determine if this is the case.

Additionally, recent changes to how Power BI Service manages export queries may impact certain functions or complex DAX logic. If the issue persists with a basic visual, it could indicate a service regression or bug.

As a temporary solution, consider using the Analyze in Excel feature (if available), creating a simpler export-friendly table for users, or utilizing DAX Studio to extract the required data directly from the model

Given that the issue affects all environments and is not exclusive to SharePoint, I recommend submitting a support ticket to Microsoft : How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

 for further investigation. Please include the error message screenshot, confirmation of failure across Desktop, Service, and SharePoint, and the steps to reproduce using your sample file. This will assist Microsoft in determining if the problem is related to a service-side change.

Thank you,

Tejaswi.

[v-tejrama]

Hi @fsinclair ,

I wanted to follow up and see if you had a chance to review the information shared. If you have any further questions or need additional assistance, feel free to reach out.

Thank you,

Tejaswi.

[v-tejrama]

Hi  @fsinclair ,

Just checking in have you been able to resolve this issue? If so, it would be greatly appreciated if you could mark the most helpful reply accordingly. This helps other community members quickly find relevant solutions.

Thank you.

[fsinclair]

Hi, 

No resolution i'm afraid. I will post about it if I have it. 

[v-tejrama]

Hi @fsinclair ,

Thank you for trying out the suggestions shared earlier. Since the issue is still not resolved, it would be best to raise a support ticket with the Microsoft product team. They have deeper visibility into the backend and can investigate the matter thoroughly to provide a proper resolution.

You can submit a support request using the following link: How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

If you do get a resolution through the support channel, we would sincerely appreciate it if you could share the outcome here in the community. This will definitely help other members who might face a similar challenge in future.

Thank you for your patience and understanding. Please continue to engage with the Fabric Community for any further questions or support needs.

Thank you,

Tejaswi.

[v-tejrama]

Hi  @fsinclair ,

I wanted to follow up and see if you had a chance to review the information shared. If you have any further questions or need additional assistance, feel free to reach out.

Thank you.

[fsinclair]

I have a support call, they haven't got back to me. Assume if I haven't posted or accepted a solution, that I don't have one 👍

[v-tejrama]

Hi @fsinclair ,

Thank you for informing me that you have not yet received a response. Please continue to monitor the forum for further updates..

Thank you,

Tejaswi.

[v-tejrama]

Hi @fsinclair ,

Thank you for providing the detailed explanation. From your description, the issue does not appear to be related to data size or model type, as you are using Import mode with a limited number of rows. The error is instead originating from the export operation within the embedded context. Due to recent backend updates in the Power BI service, exporting visuals embedded in SharePoint via the web part has become inconsistent. This explains why the functionality was previously working and has now changed in recent weeks.

To verify, please attempt to export the same visual directly from the Power BI Service, outside of SharePoint. If the export is successful there, it confirms that the limitation is specific to the embedded SharePoint view. Currently, the recommended workaround is to export directly from the Power BI Service or to share the report through a workspace or app where exporting is fully supported.

While I understand this change may be inconvenient, please be assured that your report configuration is correct; the restriction is with the export feature in SharePoint embed.

Thank you,

Tejaswi.