Forum Discussion
Error while exporting Excel using the "Summarize Data" option.
Hi,
When trying to export to Excel, some users are receiving the following error message:
No changes have been made to the report or to the underlying data model. However, starting today, some users have begun encountering this error.
The issue does not occur consistently, and it is not associated with any specific combination of measures and dimensions.
We are unsure what could have caused such a sudden issue.
thanks!
2 Replies
- DreamITLearn
Advocate I
Hi AAM_ ,
This is a known, recurring issue with Summarized Data export ("File couldn't be created" / query generation error) that others have reported too, it isn't something specific to your environment. A few things worth checking since it started suddenly with no report changes:
- Confirm whether it's tied to visuals pulling measures from multiple tables, that's the most common trigger per the error message itself.
- Check if it only fails with the "xlsx with live connection" export option specifically, other formats (CSV, current layout) often still work as a workaround.
- Rule out a recent service-side update, this error has appeared in waves for other users right after Microsoft backend changes, not local report changes.
If it's intermittent and not tied to a specific visual, it likely points to a service-side issue rather than your data model. Worth checking the Fabric/Power BI service status page for any known incidents around the date this started.
- ShivekMaharaj
Memorable Member
Hi AAM_,
There have actually been several very recent reports of this same Summarized data export error, so I think a service-side regression is a reasonable possibility here, although I wouldn't call it a confirmed Microsoft incident yet.
Microsoft's current Export data documentation states that Data with current layout and Summarized data have the same data granularity; the main difference is that Current layout preserves the visual structure while Summarized data generates a flat table.
Because of that, one of the first tests I would make is:
- export the same visual using Data with current layout
- export it using Summarized data
- compare whether only the Summarized option fails
If Current layout succeeds from the same visual, that points much more toward the summarized-export query generation than toward general permissions, RLS, or access to the semantic model.There is also a recent Fabric Community thread from this week where a matrix using Field Parameters suddenly stopped exporting Summarized data despite no changes to the report or model. Microsoft Community Support subsequently described it as a recent issue affecting summarized export for matrix visuals using Field Parameters and suggested Current layout as the temporary workaround.
So if your visual uses Field Parameters, I would try one additional isolation test: duplicate the visual and temporarily replace the parameters with the physical fields/measures currently selected. If that static version exports successfully, it would strongly suggest that you are hitting the same interaction.
I would not immediately remodel measures simply because the error message mentions measures from multiple tables. Since this started suddenly without report/model changes and is intermittent across users, I would first isolate the export mode and visual configuration.
For now I would:
- Test Data with current layout as a workaround.
- Test the same visual without Field Parameters, if applicable.
- Record which users/visuals fail and the approximate timestamps.
- If the behaviour continues, raise a Microsoft Support ticket with the report details and screenshots so Microsoft can correlate it with the recent export reports.
So yes, the timing and intermittent behaviour make a service-side issue plausible; I just wouldn't treat that as confirmed until Microsoft formally acknowledges the incident.AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.