How to integrate a Power BI report into a model driven Power App AND export into a PDF or PPT

Hi,

We have a problem with the integration of Power BI reports into a model driven Power App. We have the following requirements:

• Integration of the report into the app (no forwarding from the app to Power BI Online)
• Export the report to PDF and/or PPT. The filters and settings made by the user online should be taken into account in the export.
• Interactive Power BI reports. The user should be able to filter the report using slicers, etc.
• Deploy capable. This means that changes to the PowerBi report are made in a development environment and should be copied to the production system via deploy (manually or via pipeline).

So far, we have integrated the Power BI reports directly into the Power App (Power BI Content Management). This is a screenshot of the implementation:

From 31.07.2024, this method will no longer be supported by Microsoft https://learn.microsoft.com/en-us/power-bi/collaborate-share/service-power-bi-powerapps-integration-about.

We have therefore tried to implement the method suggested by Microsoft (via Power BI embedded system dashboard): https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/create-edit-powerbi-embedded-page.

However, the menu bar with the export option is no longer visible.

Does anone know if there is a an option to display the export menu again?

What have we done so far:

• Adding the Power Bi Report directly in the Config.XML file, as described here https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/embed-powerbi-report-in-system-form. Same result: The export bar is not displayed
• Switching the PowerBI environment to a Premium license to get access to the API and to call the PDF export itself via the REST API. But the filters set online by the user were not taken into account in the PDF. Is this possible?
  
  
• First attempts with PowerBI Embedded. Here we have the problem that we have to save the ClientSecret Token within the Power App (JScript). However, this would be visible to the end user via the browser console. Thats a nogo. Is there a method to hide the secret token? But even this is possible, this way seems much too complicated.

I think we are lost and can't see the wood for the trees at the moment.
Does anyone know a solution?

Thanks
Lars