When you send data from Power Apps to Power Automate, do you use more than one parameter?
Power Apps and Power Automate integration
Table of Contents
Within Power Apps you can send data to Power Apps using the Ask in Power Apps in dynamic content. This quite quickly means that you end up with a lot of parameters when you want to pass a lot of data to your flow. This can become quite hard to manage.
On top of this if you decide that you need an additional parameter you will have to disconnect your flow from your Power App after you added the additional parameter to your flow.
Less Parameters
In short, this can be a pain! A pain to be solved in this post.
I’m starting by creating a single input in my Flow. My input is called Compose_inputs, but you could call it anything you like.
Then in my Compose action I’m converting the json text to json object using the json function. You could of course also use the parse json action, however this will be more flexible as I might not know the exact format of my json that is sent to the flow.
In my Power App I’m adding a button that sets a variable with the json text that I want to send to Flow.
My thoughts
The method described in this post:
- Avoids having to recreate the Power Apps/Flow integration when the number of parameters change
- Avoids many parameters when running flows from Power Apps
This is really awesome!!!
Thanks for sharing your great knowledge!
From PowerApps, you can use JSON() function to convert an object to JSON string, so you don’t have to concatnate strings manually. For example,
UpdateContext({
ctxFlowParams:{
field1:TextInput1.Text,
field2:TextInput2.Text
}
});
PowerAppsButton.Run(JSON(ctxFlowParams));
Agreed. The json function can make this easier.
Hi Pieter ,
Just a thought if this button is a ribbon button what we need to do to call it from there using JS ?
Thanks
Hi Manish,
Do you mean that you want to click a button in PowerApps from outside your powerapp?
i follow exactly. the flow button in PA said expecetd 0 , received 1
I am confused by the Compose action. No “Ask in powerapps” needed?
You still need to use the ask in powerapps trigger. Use this in the compose action.