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! 👍💡

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

Nice work Shane. Keep it up! 🙌🏻

good on you Mr.Shane It shines bright

Good clear information there Shane 👍

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!

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?

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.

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 ?

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?

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.

Thanks Shane

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

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?

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

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

"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 ?

Monitor! Monitor! & some JSON pls 😊

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

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

Does removeif have the same limitation?

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.

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

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.