Answered

UpdateIf just stopped working after 10 months!

(0) Share

Report

Posted on by Sulako

Hello everyone, this is a very strange situation. Just yesterday our updateIf code just stopped working in our powerapp, no matter what we tried or did nothing would show that this code was working.

This has caused a very serious issue and a lot of time will be incurred as a result to correct this. Has anyone else had similar issues? We changed our code to Patch and everything is fine now!

Data source is SQL on premise.

No delagation limits have been incurred.

Below is a obfuscated example of our code. Update IF has been commented out due to it not functioning correctly.

Would be great to know if anyone else experienced this behaviour and if they know why it stopped working?

**************************************************

Set(varUpdate_SupLots,false);
IfError(
    
    If(!varDHSHasBeenLoaded, 
        
        ForAll(Filter(
                    lstParentChildComponentsForExport,
                    IsParent = 1 && ComponentCode = ThisRecord.ComponentCode && ThisRecord.HasLotAndExpiry && !IsBlank(ThisRecord.Lot)
                ),
                Patch(LotNumbers,LookUp(LotNumbers,LotNumber = If(EndsWith(Lot,"R"),Mid(Lot,1,Len(Lot)-1),Lot)),{IsRework:EndsWith(Lot,"R")})
                //UpdateIf(LotNumbers, LotNumber = If(EndsWith(Lot,"R"),Mid(Lot,1,Len(Lot)-1),Lot), {IsUsed:true, UsedOn:Now(), IsRework:EndsWith(Lot,"R")})
        ), 
        
        ForAll(Filter(
                    lstParentChildComponentsForExport,
                    IsParent = 1 && ComponentCode = ThisRecord.ComponentCode && ThisRecord.HasLotAndExpiry && !IsBlank(ThisRecord.Lot)
                ),
                Patch(LotNumbers,LookUp(LotNumbers,LotNumber = If(EndsWith(Lot,"R"),Mid(Lot,1,Len(Lot)-1),Lot)),{IsRework:EndsWith(Lot,"R")})
                //UpdateIf(LotNumbers, LotNumber = If(EndsWith(Lot,"R"),Mid(Lot,1,Len(Lot)-1),Lot), {IsRework:EndsWith(Lot,"R")})
        )
        );
        Set(varUpdate_SupLots,true);,
    Notify("Cannot update lot numbers (Sup Lot)")
);



************************************************** 



Thank you

Categories:

Building Power Apps

I have the same question (0)

All responses (4)

Answers (1)

Suggested answer

SebS 4,616 Moderator on at

Like (0)

Report

I think the main reason is delegations UpdateIf is not fully delegable

https://learn.microsoft.com/en-us/power-platform/release-plan/2024wave2/power-apps/enhance-delegation-updateif-removeif

Your code was working untill data reached above 2000 records than it stops cause it was not delegable :(

Was this reply helpful? Yes No
Sulako 32 on at

Like (0)

Report

This is 100% not a delegation problem. The table this update writes into is 350,000 rows big and has been for the last year. So this is definately not the cause of this problem. The filter process gets the specific row to update.

This is a major issue and the root cause needs to be established!

Hoping someone can provide information.

regards,

Was this reply helpful? Yes No
Verified answer

WarrenBelz 153,084 Most Valuable Professional on at

Like (0)

Report

@Sulako,

Just adding to @SebS's valid statement. UpdateIf in it's "native' form will only address data up to your Data Row Limit. Adding the switch

enhances the Delegation capabilities to your Data Row Limit after the condiiton has been evaluated (so it will update Data Row Limit selected records).

In your case however, you have included the action (which you have commented out in your post) inside a ForAll statement and when you do this, the limit applies to each "loop" of the ForAll data, so I am not sure how this would work for you (or did in the past).

However I will add that using Patch inside the ForAll as you have done now is a much better and more stable option.

2 people found this reply helpful.

Was this reply helpful? Yes No
Sulako 32 on at

Like (0)

Report

Thank you everyone, it turns out some numbers were added to our database which pushed the UpdateIF passed the delegation point.

Appreciate everyones help on this.

Was this reply helpful? Yes No