Unanswered

Receiving Delegation Warning from LookUp and Filter

(0) Share

Report

Posted on by ZackBakouris

Hello,

I'm relatively new to Power Apps and have been trying to get around the delegation limit for one of my projects. For some context, I've created an input tool for one of our consulting teams to use. The team using this tool enters and submits their implementation records through it, which are then stored in a Sharepoint list and fed into Power BI. The Power App has a recall feature built in where it's supposed to auto-populate with data from the most recent implementation record entry, based on the implementation's title/name and bill number. This has been working well until recently, when we first exceeded the 500 record limit. I updated the record limit to 2000 as suggested, but this is only a temporary solution.

It seems like the formulas are isolating LookUp and Filter as the sources for the delegation warnings, but I'm not sure what I could do to eliminate the delegation warning entirely.

Screenshot (161).png Screenshot (162).png

This is a larger issue that we're facing, since the number of records being generated throughout the year could easily exceed the limit of 2000, and we need to consistently bring up the most recent version of the records.

Any insight is very much appreciated. Thank you!

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (0)

adedapo 256 on at

Like (0)

Report
Copy link

Link copied!

Hmm... everthing seems perfectly delegable. Make sure to sort by the created or modified columns to get your latest data

Was this reply helpful? Yes No
ZackBakouris 2 on at

Like (0)

Report
Copy link

Link copied!

Hi @adedapo,

The sort order is adjusted properly. Is there any other piece that looks out of place? I'm not sure why Power Apps would be giving me the delegation warnings with this formula

Was this reply helpful? Yes No
adedapo 256 on at

Like (0)

Report
Copy link

Link copied!
Hello @ZackBakouris
I think the reason why you are having the warning is that you are using a couple of table shaping/summarization functions, particularly Distinct.
The problem here is that even if the filter is perfectly delegable, it will still download a maximum of the set data row limit (in your case, 2000). So, a summarization function like Distinct may not be accurate if the result set exceeds the limit.
There are a couple of ways to solve this problem:
You can load up to 4000 items in a collection and then perform your other operations on it. Only use this if you know your data is not fast growing and/or will not surpass 4000 records.

Concurrent( ClearCollect( colDataInputToolListChunk1, Sort( Filter( LRM_DATA_INPUT_TOOL_LIST, StartsWith( 'Bill #_OVERVIEW', 'TI_Bill #'.Text ) ), ID, Ascending ) ), ClearCollect( colDataInputToolListChunk2, Sort( Filter( LRM_DATA_INPUT_TOOL_LIST, StartsWith( 'Bill #_OVERVIEW', 'TI_Bill #'.Text ) ), ID, Descending ) ) ); ClearCollect( colDataInputToolList, colDataInputToolListChunk1, Filter(colDataInputToolListChunk2, Not(ID in colDataInputToolListChunk1.ID)) ); Clear(colDataInputToolListChunk1); Clear(colDataInputToolListChunk2);

Delegate to Power Automate. There you can get as much as 5000 items at a time or paginate through your records if it is more than 5000. Then you can either send back all the records after you've selected just the fields you need, or you can get the distinct values from Power Automate and send just the result.

Was this reply helpful? Yes No