How to create a button in a Model Driven (Dataverse) Power App that launches P.A. Flow in a Solution

This video explains how I was able create a button in a Model Driven (Dataverse) App that launches a Power Automate Flow in a solution. The requirement came with a few additions that made it even more tricky to implement.
1. The flow needed to know who the App user is so it can send a notification to that user.
2. The flow also needed to know which Dataverse record was selected.
3. The App and Flow in part of a solution that will be sent as a Managed Solution to Test and Production environments. So, I could not hard code the Flows URL.

[@wrajer]

thanks a lot!

[@imstillbreathing1]

I love your videos. They have helped me a lot over the last few weeks of doing projects for my company!

[@365assistdarrenlutchner9]

Thanks for the great feedback

[@ChrisMcGrory0513]

Great video! Would you be able to make another video going through the steps following the HTTP request trigger?

[@jhhood86]

I was able to get all this to work and thank you very much for explaining all this! However I'm a little fuzzy on the migration/environment variable part. I understand that when I import my solution into my clients' environment, I have to define the variables there so the URL wont exactly be generated yet. I guess I would have to do a double import? Let it generate first, get the url, then reimport to set the variable?

[@365assistdarrenlutchner9]

Perhaps you could use Environment Variables. That way you can change the variables values in the new environment.

[@okidipekimbambo]

Where can I find the JavaScript code You are using here???

[@365assistdarrenlutchner9]

Here you go - www.365-assist.com.au/jshowtocreatebutton

[@DennyEapen]

Didn't work for me.
static async CallWorkflow (executionContext:Xrm.Events.EventContext){
const formContext = executionContext.getFormContext();
}
gave the error *Uncaught (in promise) TypeError: executionContext.getFormContext is not a function*

[@DennyEapen]

Never mind 🙂
I was using EventsContext instead of FormContext.
Thank you very much