How to bypass PowerApps V2 Trigger limit of 19 pieces

[JeffT2022]

Hello,

I am trying to create a button, that would take selected values in Sharepoint List A, and create an item in Sharepoint List B.

The V2 Trigger was working well, until I hit the 19 piece limit.

I'm trying to find a work around that would allow me to move approx. 38 pieces, I read something about using Concatenate & Split, but I'm not familiar. Does that sound right to anyone else?

Any input or ideas are welcome, trying to cast a wide net.

thank you.

[RPGpro]

To answer your main question: there are a couple of ways around the limit, though you do need a premium account for the simplest methods, you could create a new flow which uses the "request" trigger, this allows you to call this flow from within another and pass data to it, this other flow could then continue to process the data and pass the results back. 

The real issue though is why you're hitting the limit on what sounds to be a simple task. 

Could you give a little more info with regards to what you're trying to accomplish and/or your current flow? 

[bloempotje]

@RPGpro could you elaborate on the 'couple of ways' i'm trying to find the simplest way around this limit but cant seem to figure it out. i need to populate a word doc with way more inputs. 

[RPGpro]

You could create a second flow using the "request" trigger type, you can then call this flow from your main one, (essentially creating a sub-process) pass data to that to the sub-flow for processing and then pass back the result. 

This would pass some of your usage over to another flow with its own separate limits. 

Another alternative is to push the data to some other external source through some connector, power apps is a good example as it integrates closely with power automate, but you could also pass the data to a custom JavaScript connector or something else, process the data over there and return the result. 

As an extension of that last point, the external source could be the power apps desktop app, which could then complete the entire process without having to send data back to the web flow (you would need the desktop version of word and oneDrive)

As a really bad but simple alternative, you could ensure that you never hit the API limits by adding a pause into your flow. 

check the API limits for the connector you're having issue with, there should be some amount of regen, for example it might gain 5 calls per 10 seconds. 

Add a "wait" action to your flow to ensure it doesn't go over this limit, given the above example you would need to add a 2 second wait after each action that uses that connector. 

This will of course slow down the flow by a massive amount, but it's an easy solution if you're not bothered about execution time. 

If you're adding data to word, make sure you compile all the data within the flow and then add it to word in a single action, rather than doing small edits with each individual data part. 

For example, if you're processing business card info with 3 inputs: name; job; phone:

Don't do:

read the name -> save to word -> read the job -> save to word -> read the phone -> save to word -> next card -> repeat till no cards left. 

Instead do:

read the name -> save to a variable -> read the job -> append to the same variable -> read the phone -> append to the same variable -> next card -> repeat till no cards left-> save the variable to word. 

Any external connections (including the connection to office365 word) tend to be where you hit API limits and are also the parts that slow down your flows. 

[bloempotje]

thanks for the input! for the first option, do you mean the http request?

[RPGpro]

---

@bloempotje wrote:

do you mean the http request?

---

Yes, from what I've seen on here it seems to be the most commonly used method for triggering one flow from another. 

[bloempotje]

thanks for the quick reply, at this moment ive used the parse json method which seems to work but......
do you know anything about a 'set' function and '.run' function in the same 'onselect' button?

Set(
TestInfo;
JSON({
Kenteken: TextInput_1.Text;
TypeAfspraak: Combobox_2.Selected.Value;
Merk: Textinput_3.Text;
Klantnaam: TextInput_4.Text;
CSM: ComboBox_5.Selected.Value;
AangemaaktDoor: TextInput_6.Text;
Partij: Combobox_7.Selected.Value;
Model: TextInput_8.Text;
Hardware: ComboBox_9.Selected.Value;
UitvoerDatum: Date_10.SelectedDate;
VerkoopOrdernr: TextInput_11.Text;
NieuwIMEI: TextInput_12.Text;
OudIMEI: TextInput_13.Text;
JC1: jc1.Text;
JC2: jc2.Text;
NC1: nc1.Text;
NC2: nc2.Text
})
PowerAppsRun(power)
)

[RPGpro]

I just noticed that this question was originally regarding limits to number of blocks, not number of calls (hence several of my suggestions mentioning API limits), oops. 

The simplest way around this limit would be to have powerApps compile all the data into a single JSON (or plain text CSV if you don't like JSON) object and pass that as a single argument to the power automate flow, which appears to be the solution you came up with. 

I'm not particularly well-versed with the language powerApps uses, but... in theory it just executes the code sequentially no matter whether it's in an "onSelect" function or elsewhere, it looks like you're maybe missing a closing bracket after the JSON data? (the run function is inside the set function) 

Otherwise it might be best to open a new thread for that question. 

[bloempotje]

@RPGpro thanks for the help!