Solved: Re: How to Submit Form and Run Power Automate at S...

Travis5150 · ‎01-10-2022

Here is my Power App.

The user will fill in the information, and click submit.

The submit button OnSelect is Submitform(Editform1).

This information is then put into a SharePoint List.

What I would like to do, if it is possible, is when they click on Submit, the same action happens with the SPO site, but I would like for a FLOW to be kicked off.

The FLOW will post a message to a teams chat. I would like it to post the information they are submitting in the form from the PowerApp.

I found how to kick off the flow, but it takes away my submitform. Can I add multiple lines to OnSelect?

So my goal is, for the Power App to submit the information that it is doing right now SPO List, as well as kick off a flow (above) that will post a message to a chat in Teams, but use the information from the form.

Any idea how I accomplish this?

RandyHayes · ‎01-10-2022

@Travis5150

If it is a choice column, then providing just that column name is a record (choice columns are records). So, to get the text value, change that from Self.LastSubmit.CaseType to Self.LastSubmit.CaseType.Value

As for the PowerAutomate flow - yes, it is actually better to provide a JSON string to the flow rather than individual parameters. This makes it easier to change as time goes and you need to change as you don't have to alter the flow parameter signature to the app and thus go through the removing and adding the flow again for PowerApps to recognize it properly.

You don't need in-memory databases (collections) to do this. It can all be done from the formula.

i.e. 'TEST-CasePost'.Run(JSON({CaseNumber: Self.LastSubmit.CaseNumber, CaseType: Self.LastSubmit.CastType.Value}))

The above will send a JSON string to the flow.

This is preferred over trying to do it in a collection or anything like that (not to mention that is way more work than you need to do). The reason it is preferred is if you change the values you want to pass to the flow down the road, it is all right there in the formula. No need to hunt down collections and how they are populated.

As for the PowerAutomate parse json...you need to supply a Schema for the JSON. Once you do that, then you have access to all the columns parsed.

Based on the example that I provided for the flow signature in the above formulas, in your ParseJSON action, you would "Generate from sample" and provide the following for a sample:

{CaseNumber:123, CaseType:"abc"}

It will now create a valid schema for that in the Parse JSON action.

Now, anywhere in the flow you can reference the "Parse JSON" action and then you will see CaseNumber and CaseType.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes
Really want to show your appreciation? Buy Me A Cup Of Coffee!

View solution in original post

RandyHayes · ‎01-11-2022

@Travis5150

I'm not sure why you would want to take two values and put them into an in-memory database table (the collection). You already have the values, just pass them in the JSON.

As mentioned, your OnSuccess formula should be:

'TEST-CasePost'.Run(
    JSON(
        {CaseNumber: Self.LastSubmit.CaseNumber, 
         CaseType: Self.LastSubmit.CastType.Value
        }
    )
);
Back()

There just is not need to set variables and make collections...you already have what you need ready to go.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes
Really want to show your appreciation? Buy Me A Cup Of Coffee!

View solution in original post

RandyHayes · ‎01-10-2022

@Travis5150

You can call your flow from the OnSuccess action of your form.

From there you will also have access to the Self.LastSubmit which will be the record that was submitted from the form. So all columns are available from that to pass to your flow.

I hope this is helpful for you.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes
Really want to show your appreciation? Buy Me A Cup Of Coffee!

Travis5150 · ‎01-10-2022

Ok, I need to step through this one piece at a time.

For the On Success, I have the back action to take me back to the main screen.

So I added a ; after that so I can add the action for the flow.

Now with the flow, it tells me invalid number of arguments, received 1, expected 3.

So I tried three, then it just said error.

I would like for it to pull out the Title(which is the case number), and CaseType.

Once we get this to work, we can then work on passing the values to PowerAutomate.

Where am I going wrong here?

RandyHayes · ‎01-10-2022

@Travis5150

I'd recommend putting the Back() last in your formula - just makes it clearer to read.

Your parameters for your flow run are going to be dependent on how you have built the flow.

If it is saying that it is expecting 3 parameters, then you have defined 3 "Ask In PowerApps" options in the flow.

When you type the name of your flow and then .Run( - immediately at that point, the formula editor will tell you the three parameters it is expecting in the formula hints.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes
Really want to show your appreciation? Buy Me A Cup Of Coffee!

Travis5150 · ‎01-10-2022

So, same issue.

I went back in and redid the Flow.

I chose Ask in PowerApps. It then filled in the field as seen in the pic below.

if I go back into dynamic, I also now see that "Postmessageinachatorchannel_Message" after I did the Ask in Power Apps.

In PowerApps, I am still getting the invalid arguments.

RandyHayes · ‎01-10-2022

@Travis5150

Will in the case of the formula you have...there is an error! You only need Self.LastSubmit.Title The .txt is not relevant and is an error.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes
Really want to show your appreciation? Buy Me A Cup Of Coffee!

Travis5150 · ‎01-10-2022

Yep, you beat me to it! I was just getting ready to post that I fixed it.

i went back into the Flow, click on Ask Power Apps once.

Went into the Power App and was able to get it to post what I wanted.

Now, I need it to post another value from my form though.

So I went back into the Flow, and clicked on Ask Power Apps for a second time.

I tried to add the second value, but it keeps giving me the invalid arguments.

How do I pass the two values in? I thought they would just be seperated by a comma, but I could be wrong.

Travis5150 · ‎01-10-2022

Getting closer.

So this works...BUT it sends the wrong values lol

RandyHayes · ‎01-10-2022

@Travis5150

Get rid of the double quotes around the parameters. When you do that, you are just sending what is in the quotes as the text that is seen, not the column value that you want.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes
Really want to show your appreciation? Buy Me A Cup Of Coffee!