Deployment Pipeline of Report with Embedded PowerApp

[Anonymous]

Hello Experts,

I am interested to understand the best practices when attempting to deploy a powerBI report that has an embedded power app and flow. Below is my current thought process, and I hope someone can help me understand further. The current PowerBI application behaves as such: (PowerApp in PowerBI Dashboard --> User Selects Button on Power App --> Flow is Executed --> Data is Loaded --> PowerBi Dashboard is Refreshed)

Deployment Thought Process:

PowerBI report and dataset will be deployed through a deployment pipeline. This allows the report/ dataset to point at our production instance and oneclick deployments.
PowerApp and flow will have to be deployed through an environment. This will allow us to establish our connections at the environment level and not expose these connections to other users.
Lastly, I would assume that we need a way to point the production PowerBI report to the production instance of the powerapp. I am completely lost on this piece and would like to understand how this is possible.
Any documentation that could be provided would also be beneficial.

Best Regards,

Dakota

[jankonas]

Has anybody solve this issue?

When I deploy a report with embedded Power App, it seems that the Power App is related to both reports (DEV and UAT). Is is possible to change it? Let's say, the DEV report will communicate with DEV Power App,  the UAT report will communicate with UAT Power App. The App will know where to do the write-back (which database). Right now, I have no clue how to set this up and haven't found any relevant tutorials. This is quite important to obtain.

Many thanks

[jankonas]

I have analyzed the issue with Microsoft and other companies and there is no smart solution for this topic.

The best workaround is to have all three apps on the report page and show/hide the appropriate one on each workspace. You need to edit the report, show selection pane in the view tab and show the right app after each deplyoment. Unfortunatelly you have to do it everytime and the deployment pipeline looks broken as the reports don't match after the change.

It seems there is no plan to fix this issue but hopefully one will come soon as this is quite crucial and a terrible mistake can happen easily.

[garthmcdonald1]

Is there any progress on this issue?  We have the same issue and we had hoped to parameterize the Power App URL and use a Pipeline rule but this does not appear to be supported.  Is tis on the develpment roadmap as this requirment is not uncommon and there is no elegant solution.

[v-xulin-mstf]

Hi @Anonymous,

Is your issue solved? If the issue has been solved, please adopt the solution to help others.

If you still have some question, please don't hesitate to let me known.‌‌

Best Regards,

Link

Is that the answer you're looking for? If this post helps, then please consider Accept it as the solution. Really appreciate!

[Anonymous]

Hello @v-xulin-mstf , I am stuck on another bottleneck at the moment, and have not been able to implement the solution yet. I will follow back up when necessary. Thank you. 

[v-xulin-mstf]

Hi @Anonymous,

I haven't heard from you for a long time, did you solve your issue?

If you still have some question, please don't hesitate to let me known.‌‌

😉

Best Regards,

Link

Is that the answer you're looking for? If this post helps, then please consider Accept it as the solution. Really appreciate!

[v-xulin-mstf]

Hi @Anonymous

You can refer this to get started with deployment pipelines.

Considering your comments about you need a way to point the production PowerBI report to the production instance of the powerapp.

Maybe you can integrate with Power Apps in Power BI first.

Please refer:

https://purple.telstra.com/blog/powerbi-integration-with-powerapps

If you still have some question, please don't hesitate to let me known.‌‌

Best Regards,

Link

Is that the answer you're looking for? If this post helps, then please consider Accept it as the solution. Really appreciate!