Error while exporting Excel using the "Summarize Data" option.

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:

1. Test Data with current layout as a workaround.
2. Test the same visual without Field Parameters, if applicable.
3. Record which users/visuals fail and the approximate timestamps.
4. 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.