cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Helper V
Helper V

How to trigger Flow with ForAll

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.

parameters.PNG

highly appreciated for your help. 

3 REPLIES 3
Highlighted
Resolver I
Resolver I

Re: How to trigger Flow with ForAll

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?

Highlighted
Helper V
Helper V

Re: How to trigger Flow with ForAll

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/h...

 

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  

Highlighted
Resolver I
Resolver I

Re: How to trigger Flow with ForAll

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.

Helpful resources

Announcements
August 2020 Community Challenge: Can You Solve These?

August 2020 Community Challenge: Can You Solve These?

We're excited to announce our first cross-community 'Can You Solve These?' challenge!

secondImage

Return to Workplace

Reopen responsibly, monitor intelligently, and protect continuously with solutions for a safer work environment.

secondImage

Super Users Coming in August

We are excited for the next Super User season.

secondImage

Community User Group Member Badges

FIll out a quick form to claim your community user group member badge today!

secondImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

Users online (8,048)