Export Data Failure

[parkergeis]

Hello, we have recently transitioned a report from a model using import to a model using Direct Lake storage mode. When in Power BI Service, the report behaves the exact same (with the added Direct Lake benefits of course). However, when this report is interacted with via our embedded environment, we are unable to export any visuals' data. The above picture shows the error we receive. 

This exact export (same amount of data, same visual, same environment, same workspace) works when the report is connected to the import model, but has troubles when the Direct Lake model is connected. The report exports just fine in the service interactions and we only have issues in the embedded environment.

Has anyone come across this issue before or have any tips for items to look for in the troubleshooting process?

[vince-saelzler]

It is possible to export data in your embedded scenario by specifying a fixed identity for the connnector between the model and the SQL analytics endpoint of the lakehouse.

From the fabric workspace, click the ellipses on the semantic model, then

• Settings > Gateway and Cloud Connections > Cloud Connections

Change from the default of using Entra SSO. Create a connector as described in Microsoft Learn

[parkergeis]

I had already done that in order for our embedded environment to reach the report without error. It did not fix the export issue unfortunately

[Anonymous · Accepted solution]

Hi @parkergeis,

Thanks for reaching out to the Microsoft fabric community forum.

You're right, the exporting data works fine in the Power BI Service even after switching to Direct Lake. The limitation you’re running into appears to be specific to the Power BI Embedded experience.

Currently, there are known gaps in feature parity between reports using Direct Lake and how they behave when embedded, especially with actions like exporting data from visuals. While this functionality is supported in the Power BI Service, it doesn’t seem to be fully supported yet in embedded environments when using Direct Lake mode.

To be clear, Direct Lake itself doesn’t block exporting data, but the embedded export functionality seems to hit a limitation (or possibly a backend constraint) when used with Direct Lake models. This wasn’t the case with Import mode, which explains why things worked previously.

We’d recommend logging this behavior with Microsoft Support or via your Power BI support channel, especially if this impacts production use. In the meantime, if exporting is essential from the embedded report, you may need to temporarily use Import mode or explore workarounds like offering data downloads via APIs or paginated reports until full support is rolled out.

To reach out to Microsoft Support by raising a ticket with Microsoft Support, please refer below link on how to raise a contact support or support ticket.
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

I would also take a moment to thank @SolomonovAnton, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.

If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

Best Regards,
Hammad.
Community Support Team

If this post helps then please mark it as a solution, so that other members find it more quickly.

Thank you.

[SolomonovAnton]

Unfortunately, after switching the model to Direct Lake storage mode, the Power Bi will not allow you to download data.

✔️ If my message helped solve your issue, please mark it as Resolved!

👍 If it was helpful, consider giving it a Kudos!

[parkergeis]

Thank you for the reply. I have no issue downloading the data from the same report in PBI Service - are you sure about the "the Power Bi will not allow you to download data" statement?