Can't export power bi report that uses lakehouse semantic model through Power Automate.

[GaryH]

All,

I am trying to run an automated process the exports a Power BI report to a PDF and emails it.  We have dozens of Power Automate jobs that do this currently without issue.  However we have tried with a report that is using a LakeHouse DataSet and this receives an error after almost exactly 30 seconds.

This error contains the following details: "Generating export content failed for section 2 due to InvalidRequest. Message: failed to load page request url"

The Power Automate job fails on the "Export To File for Power BI Reports".  I've selected PNG, below, but all other formats fail also.

any ideas would be appreciated.

[kikipmtgf]

Hi,

I have the exact same issue. Have you been able to solve yours?

Thanks.

[GaryH]

Unforrunately no.  I had a ticket open for over 2 months on this, and they couldn't even provide an estimate of when it would be fixed as internally it involved multiple teams.

The only workaround provided was to use the subscribe feature directly in the power bi service to email reports out.  Unfortunately we have a more advanced workflow in power automate, so this wasn't a viable workaround.  

One thing I did discover is paginated reports "do" work if thats an option for you.

For now, we have moved these reports off lakehouse fabric for now until we can see the system is feature complete and stable.

[kikipmtgf]

Hello,

I just got an update from Microsoft. Here it is:

"I would like to inform you that, I have received an updated from product team. They mentioned that, Direct lake models/reports aren't supported in embed scenario when the model is configured as SSO connection. Since Export to File API is using embed token "behind the scenes", this limitation also applies to the API. Possible mitigation for allowing Export to File scenario for the you is trying to use fixed identity instead of SSO for his model Learn how to specify a fixed identity for a Direct Lake semantic model in Power BI and Microsoft Fab.... It makes sense that the export works from Power BI portal, since when exporting from the portal the implementation isn't done with embed token, so the scenario is supported. So, it is by design behavior."

I will investigate their proposed mitigation.

[kikipmtgf]

Thanks for your reply - hopefully they will fix this at some foreseeable point. I am in the same case as you, the subscribe feature does not fulfill the need.

[GaryH]

Thanks for replyhing.  Yes, same error running directly through the api in the sandbox. 

I've also completed some additional tests.  I also added a table to the report to force direct query instead of direct lake, and the automate job now runs, but with all table/charts all the grey box with "can't display the visuals". Definity something with the api not connecting the lakehouse. 

[lbendlin]

If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi - otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .

[lbendlin]

Do you get the same error when you try this from the API sandbox?