How to trigger Flow with ForAll

(0) Share

Report

Posted on by Community Power Pla...

Hi Mates,

i would like to call flow with ForAll, but normally its not throws error, but when run the flow then it show error

Yes as you see we need two input parameters from Powerapps to Flow, how refer intStartnum, intCount parameters.

highly appreciated for your help.

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (3)

Answers (0)

cchannon 4,702 Moderator on at

Like (0)

Report

Have you confirmed that the flow is designed to take both those input elements as written? The error message doesn't report as though ForAll is your issue, it seems to say that there's something wrong with the second input parameter. If you pull it out of the ForAll statement and just test it for a single row, e.g. PowerAppsbutton.Run(8,2), do you get a more helpful error message?

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report
Hi @cchannon
Thanks for reply,
some how issue is fixed with help of our mate
https://powerusers.microsoft.com/t5/Building-Power-Apps/How-to-trigger-Flow-with-ForAll/m-p/599783/highlight/false#M188530

but now issue Calling Long running calls in powerapps
please check here link getting same error.
if you see below code
ClearCollect( myTable, Table( { StarNumber:1, QuantityMigrate: 20 }, { StarNumber:100, QuantityMigrate: 100 } ) ); ForAll(myTable, PowerAppsbutton.Run(QuantityMigrate,StarNumber))
here startNumber, QuantityMigrate is input parameters for Excel connector, to setup Top Count , Skip Count.

so as per above it will start from 1st item/records it will copy 20 records from 1-20 working here fine
where here
starting from 100 record , then it has to copy 100 records from 100 to 200 but here it throws error that is what i pasted the link above.
Can you help me here

Was this reply helpful? Yes No
cchannon 4,702 Moderator on at

Like (0)

Report

If the call is too long for PowerApps to await the response, then the only thing you can do about it is let the call run asynchronously in the background.

Instead of calling your PowerAutomate flow with the template button, you could instead call it with a HTTP request. Then the first step in your flow after receiving the request can be to send a 202 response to say the request has been accepted and will be managed in the background. Bonus: if you handle it this way, you can structure the payload any way you want, so instead of passing your requests one at a time, you could send them all at once in a single array of arrays. That will make the app super-fast and responsive, even if it takes a minute or two to actually do the work.

Was this reply helpful? Yes No