Answered

Call flow from power apps with a lot of information need input

(0) Share

Report

Posted on by Casey_W

i want to call a flow from power apps. but the information need input is not as any guidance shows. it's too long, include like SharePoint sites address, list name, created item, send the email to ...

Could anyone help me ? if what set up of my is wrong ? It seems from guidance only the variable created from flow will be ask for input. Thanks a lot.

Categories:

Building Power Apps

All responses (3)

Answers (1)

Sort by

Pstork1 69,661 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!
The problem with a long list of input parameters when calling a flow is that the parameters have to be entered in the correct order. To avoid this problem I consolidate all the input in Power Apps as a record in a variable. Then I use JSON() to send that variable as a single JSON object to the flow as a single parameter. In the flow Use Parse JSON to get the individual values out of the object. Use those values in place of the original list of parameters.

To remove the current list of input parameters you can remove and replace the trigger. That will wipe out the existing parameter and let you add one parameter to a Parse JSON.

Here's an example of the kind of code you use in Power apps

Set(myJSON,{SiteAdd: "https://........", LibraryName: "Test", Anothervalue: "test" ...}); flowname.run(JSON(myJSON,JSONFormat.Compact));

Then parse that JSON in Power Apps and you will have access to each value added to myJSON.
Casey_W 41 on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks Sir, but why my account need input these information ? it's due to my license ? Thanks.
Verified answer

Pstork1 69,661 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!

It has nothing to do with your license. You are invoking a flow that has been setup to use a large number of parameters. If you created the flow then you specified which parameters needed to be passed. You need to pass those parameters to the flow in a specific order. Unfortunately, the intellisense prompt in Power Apps truncates the list. So its hard to see what the order should be. When confronted with this issue its much easier to package all the parameters up in a single object using names for each property. Then you can pass one parameter to the flow and unpack it there.