Power Apps UpdateIf - How to use and how to deal with it NOT being delegable

Shane should have a playlist dedicated to all Power FX functions that are not delegable without blue triangle. Good job Shane! 👍💡

[@ShanesCows]

There is a few for sure. I have thought about a functions playlist :)

[@guyw.9410]

Just Wow! Great video Shane! +1 for the monitor video!

[@ShanesCows]

Thanks guy! 🐶

[@JemicoTX]

Perhaps the consideration of delegable vs non-delegable (ForAll vs UpdateIf) is a moot point if connecting to a Sharepoint List / Table as a data source due to Collect being limited (by SharePoint) to retrieving the first 2000 rows. Understandably, the filter condition on the collect helps manage “hitting the wall”, but such “crossing fingers” shouldn’t be the mitigation to these limits. The best takeaway from the video is for PowerApp builders to understand the “rules of delegation” behind their data sources. Great Video Shane!

[@ShanesCows]

Thanks Jeff, I agree. Understanding is the most important part!

[@gerfer6261]

good on you Mr.Shane It shines bright

[@ShanesCows]

Thanks 🙏

[@Recker096]

Nice work Shane. Keep it up! 🙌🏻

[@ShanesCows]

Thank you 🙌

[@AdamBeaton-no1ug]

Hi Shane, With the ForAll approach, we still run into the delegation limit. ForAll doesn't support delegation and ClearCollect only gets the records up to the delegation limit.

[@ShanesCows]

Adam what are you trying to do exactly? Maybe I have some other ideas? If it is massive, bulk updates to thousands of items, probably better to send the update to flow and have flow do the work.

[@djpowerage]

Thanks Shane, another great video. I'm learning loads and building great company apps. Where I normally use Excel to produce reports from my Excel data I now need to use my PowerApps to have fancy printable reports. Could you do a new version of PowerBi and FLow to create reports video?

[@LivnMyLifazBestIKan]

That sounds great! I'll be looking out for that as well.

[@stuartrobinson1658]

Good clear information there Shane 👍

[@ShanesCows]

Glad it was helpful!

[@CarFinanceSimplified]

Still not entirely sure what the differences are between Patch(DataSource(Lookup…..) and UpdateIf(DataSource…..) Which is best to use? Many thanks!

[@ShanesCows]

Patch is typically used to update a single record, UpdateIf is used to update multiple records based on your criteria.

[@CarFinanceSimplified]

@@ShanesCows Just noticed that UpdateIf is now delegable in experimental features?

[@yuanhengfang3169]

Hi, Shane, another good video! I have a question about how to deal with "RemoveIf" with it NOT being delegable, do you have any good solution?

[@ShanesCows]

If you are doing mass data changes (like a bunch of deletes) might be better to send it over to flow and let flow do it. Flow is better at long running operations. Just an idea to consider.

[@yuanhengfang3169]

@@ShanesCows I agree with you, Shane. I have tried to use flow but it is a little slow. thanks!

[@iulianburlacu]

"Power Apps collections are limited to a size of 2,000 records unless you know the special techniques needed to go past that number". That being said you still cant load more then the limit of records (500-2000). Am I missing something or whats the point of putting data in a collection if Filter function brings in 5000 records for example ?

[@ShanesCows]

Collections are useful for caching data that isn't going to change. They are also nice if you want to collect and edit table data before pushing it to the data source. And they are required if you want to work with offline. So not helpful here necessarily but they do have a place.

[@ResponsibleXI]

So just avoid using UpdateIf if we are sure our datasource crosses delegable limit? And use ForAll?

[@ShanesCows]

I think yes.

[@antonioverga1541]

Does removeif have the same limitation?

[@ShanesCows]

I do believe so but I haven’t confirmed.

[@antonioverga1541]

Thanks

[@edersonti]

Master Shane, I was using the patch command passing two parameters. TABLE and COLLECTION I manipulated my collection in the app and in the end recorded it in the table in the command below. This stopped working today. Patch(Table;ColTable) Did I do something wrong ?

[@ShanesCows]

I have never used that one. What if you try Collect(table, collection)

[@louiscutmore]

Monitor! Monitor! & some JSON pls 😊

[@ShanesCows]

Got it!

[@balazsbatta575]

Thanks for the video. Do you have any idea how I can set UpdateIf to update only the first line? Is it possible? Previously I tried to use patch and update but I was not able to attach document to the Sharepoint line. UpdateIf can do it but updates all Sharepoint lines.

[@PowerThingsWithWes]

Hey Shane, How do you think the UpdateIf function would work against a local (offline) collection?

[@ShanesCows]

It would skip the step of fetching the first 500 records from the data source. It will update your data in the collection as you would suspect without issue.

[@PowerThingsWithWes]

@@ShanesCows sweet, that's how I was using it!

[@sundrapillay6668]

Thanks Shane

[@ShanesCows]

Of course :)

[@mozgus79ify]

Hi Shane, another great video. I was just wondering if we get the same delegation issue using ClearCollect /ForAll/Patch? For example the Giant list has 10000 rows, 2010 is Yellow and you want to change them to Blue. ClearCollect will only collect 2000 records which we'll update using ForAll/Patch. 10 records won't be updated. Am I correct? Would it be a good solution to run this twice (or several times for even bigger data source) or is there another way to do it?

[@ShanesCows]

I don't know. I need to ponder on this for a bit. I think the answer might be if you really wanted to update 10000 items would be to use Flow.

[@paulkroon]

You could use a toggle. Then at the end of your formula you put an if statement, use countrows to check if the amount of rows is same as the max rows (500-2000). If so then you trigger the toggle again for which you use a bolean variable to run the next batch.

[@ruslanvaleev169]

ClearCollect, according to official MS documentation, is not delegable. I wonder then if it'd help with the delegation issue created by UpdateIf. The formula with ForAll & Patch can be like this: ForAll(Filter(Table, Column = "x"),Patch(Table,ThisRecord,{Column: "y"})). By the way, ClearCollect is another pesky non-delegable function that doesn't give a yellow triangle :(

[@stephendarier1390]

Nice video.... here's a push please make a video on monitoring please please 🙏

[@ShanesCows]

Noted. Thanks Stephen.

[@vickymishra3520]

Hii Shane sorry to disturb you plz can you make video on excel add ins using api to show like stock price on in excel

[@ShanesCows]

Hey Vicky I have never done that with Excel so I am no help. Sorry

[@bgergoe]

There's one statement not fully accurate: If you use a condition like this: Category="Other" ...then ALL the records will be filtered first, and only if the number of returned rows is higher than the data row limit (500/2k), then the results will be incomplete. If however you use a condition like this: Left(Category,3)="Oth" ...then it will only filter the first 500/2k rows, because the Left() function in the condition is not delegable. So, in a nutshell, if you use a condition, that the Filter() function highlights as non-delegable, then it won't be delegable here either, and it won't warn you either, but if the Filter() function does not highlight it as non-delegable, then you only need to worry, if the number of returned rows is above 500/2k.

[@omarmoutallik9131]

that's interesting. thank you for clarification

[@LivnMyLifazBestIKan]

Shane, love your videos but the blurriness kills me when you're writing script or formulas...

[@ShanesCows]

When do you have bluryness? All of the videos are recorded in high definition. Maybe you YT settings have reduced it?

[@LivnMyLifazBestIKan]

@@ShanesCows oooo I'll check it out!! I hope that's the case. I'll try to adjust the settings asap and try it out. Thanks Shane! 😊 Keep up the awesomeness 👌 and thank you again

[@rhalesdev]

Thanks for the video. Also when you save something in a collection it will only go to the limit in settings. For me, it was 2000. It pays to know if you are updating or doing aggregates (counts, sums, etc). OR... weeks of debugging and Premier Support debates.