Use the Power Automate v2 Trigger for Power Apps

#PowerPlatform #powerautomate

You're going to learn how to adapt to the changes in Power Apps and Power Automate, specifically the shift from the V1 to the V2 connector for triggering flows. The video walks you through the differences between the V1 and V2 connectors, how to set them up, and how to pass different types of data, including files. It also provides a workaround if you still want to use the V1 connector. Towards the end, the video dives into file uploads, showing you three different ways to upload files using both V1 and V2 connectors.

Up your Power Apps Skills Today!

0:00 Power Automate v2 trigger intro
0:56 Create a flow and add the trigger
1:33 What is the main difference
3:17 The types of Input
8:26 The new file input
11:31 Edit with new designer
12:24 Create new V1 Trigger
13:17 File Uploading with v2 trigger

If you need some help with something you are working on, contact us!

PowerApps911

Let's connect on social!

[YouCanDoBetterThanThis]

I was literally scratching my head when the 'Ask in Power Apps' dynamic is missing! Microsoft is not giving enough heads-up on this! Huge thanks to Shane for uploading this helper video so timely. Sorry that you are not as lucky as the rest of us are to have a 'Shane Young' video to turn to when such nuisance occurs...LOL...

[kittsat]

I just came from your old video and the amount that I just screamed because I finally got this to work is on another level!!!! Thank you thank you thank you!!!

[MVillasin]

I just wanted something simple - press a button in Power Apps to trigger a flow that sends an email with details in a specific record in a SharePoint list. This was a headbanger until I saw this video. Thanks a million, Shane! BTW, V1 must have been permanently banished since this video was published - now no matter what I do it's v2 or nothing.

[ikacatfish]

I tried to use a Power Apps trigger for the first-time last week and could not find any instructions on how to use it that matched v2. Although I ended up finding your work around for v2, I found a different solution which was probably better for my use case. This is timely and something I will use in the future, thanks for the video!

[apbosh]

Thanks for keeping me up to date! Saves an awkward moment down the road.

[dougydoe]

Great Stuff, Shane. I've been using the V2 for a while and I prefer that anyway so all good. I think the V2 version of file upload is much sleeker, straightforward and easy to use. Thanks for sharing. Very good to know.

[TheKermit]

cheers Shane, love it when they introduce more powerful versions of a function that simplifies everything - no more JSON/Base64/Binary conversions on file attachments.

[Five_to_Nine]

You've helped countless times with pieces of info like this, thank you so much!

[adrianthomas]

Thanks you so much, this was doing my head in. my current flow recently broke (requesting 97 arguments for reasons unknown).

[fam.giannakisflores]

Shane. How pass and array?so we can upload multiples files at once? Could be as a json format? Or concatenet text?

[PrithviChandrasekar]

Hi Shane. Thank you for this video. How do you dynamically create a folder and put a file inside that folder in power apps v2?

[KyleMSchroeder]

Couple things, I've noticed about the new trigger. First, in the case that you make an input optional, you will want to manually write out the expression to reference to the input. Using the dynamic content selector excludes the question mark in the expression, which means it expects a value. For example, the dynamic content selector will return triggerBody()['text']. To avoid the error you had in your example, you will want to manually type triggerBody()?['text']. The ? means that the value can be null. The other thing I've noticed is that we can no longer pass in objects or arrays. This is a major step backwards in my opinion as I have a number of situations where I need to pass in an object or an array. I will be copying one of my workflows that uses the V1 trigger in order to retain this functionality. Hopefully, Microsoft will add those input types in the future.

[cvkealey]

What annoys me about the V2 trigger (and most, if not all of the other "Instant" triggers) is that once you add an Input, you can't delete it without deleting and re-adding the trigger. I totally get that allowing makers to delete inputs could cause problems in the flow, but there are times you really do need to delete an input. Maybe you create it as text, then realize it needs to be a number (or boolean, or whatever). Grrr!

[larryjamespaa]

Hi Shane, how about adding collection, is it under text or file? Thanks

[stuart-saunders]

Great as always Shane. Is there anything we lose as a result of the v1 deprecation??

[kenny]

Hi Shane, do you know if this trigger file input can be used for multiple files?

[Bekesam]

Thank you Shane for the heads up!! For the V2 upload, is there a gain in upload processing time or would it be the same as V1? Cheers

[michaell]

You mention at ~8:18 that you can pass variables to call text. If I have a variable that holds multiple values (text field, dropdowns), how could I pass that through? This is super helpful, thank you so much Shane.

[jaded]

Is there someplace that Microsoft warns us of these changes in Flow? I would love to know what they intend before I get my coffee and find out my life was turned upside down yet again :P

[THEDTSMAN]

Yes Thank you, this was driving me Dam you Microsoft 😊👏🏻