Answered

Delegation warning

(0) Share

Report

Posted on by consultantlk

Hi Everyone,

We have built an app that is working perfectly fine in our environment, however after being deployed to the clients environment it does not work properly or obtain data accurately. We believe it is due to all the delegation warnings throughout the app as their datasets are huge. It appears most of the delegation warnings are for the isempty() or isblank() functions on option sets and lookups. Does anyone have any ideas on how to tackle this issue. Much appreciated. Thanks!

Categories:

Building Power Apps

All responses (9)

Answers (1)

Sort by

RezaDorrani 12,145 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @consultantlk

Lists out all delegable functions with respect to CDS as a data source

https://docs.microsoft.com/en-us/connectors/commondataservice/

If you want to know what is delegation -

https://www.youtube.com/playlist?list=PLTyFh-qDKAiE6ia-D94Qk5-AzpN4dqOmD

--------------------------------------------------------------------------------
If this post helps answer your question, please click on “Accept as Solution” to help other members find it more quickly. If you thought this post was helpful, please give it a Thumbs Up.

Thanks,
Reza Dorrani, MVP
YouTube
Twitter
mdevaney 29,993 Moderator on at

Like
a
(2)

Report
Copy link

Link copied!

@consultantlk

Here's the full list of functions that can be delegated in the Common Data Service. You will need to look for any delegation warnings in your app and make adjustments using only the functions below.

Pro-tip: when developing an app always set the delegation limit to 1 in advanced settings. This way you will know if the app will break when there are more than 2,000 records.

Link to MS Documenation

https://docs.microsoft.com/en-us/connectors/commondataservice/

---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."
Pstork1 69,665 Most Valuable Professional on at

Like
a
(2)

Report
Copy link

Link copied!
If you look at the documentation that @RezaDorrani and @mdevaney have referenced there is a footnote that says for Options sets you have to test them by using comparisons.

Filter(EntityName, MyCol = Blank())

Which would be the equivalent of the isEmpty or isBlank function.
Verified answer

yeinerlop Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hello @consultantlk try to increase how many rows are retrieved by default is 500, you can use 2000
mdevaney 29,993 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

@Yeiner

While doing that might solve the immediate problem the OP will want to build an app that he can walk away from and know they will be OK if they exceed the 2,000 row limit
mdevaney 29,993 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

@consultantlk

Will your client’s SharePoint list exceed 2,000 rows some point in the future? If yes, please be advised that the answer you marked as a solution is only a temporary fix.
Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @mdevaney , @Yeiner ,

Quick question for clarification: When it says it might not work on a large dataset, what does the warning mean? Let's say the limit is set to 500 rows, then which one of the following holds true?

Will PowerApps not be able to filter a dataset which has more than 500 rows?
or
Will PowerApps not be able to display more than 500 rows, no matter how big the dataset is?

Regards,
Aakash
mdevaney 29,993 Moderator on at

Like
a
(1)

Report
Copy link

Link copied!
@Anonymous
When the warning appears it means:

"PowerApps will perform the FILTER operation only on the 1st 500 rows of the datasource and return the result. The FILTER will not be performed on the 501st row and beyond and those records will be missing from the result."

The advice of @Yeiner will only work if your dataset is below the delegation limit. Therefore, you should always try to solve the underlying problem by using functions that can be delegated first if possible. Increasing the delegation limit should only be used in 2 scenarios:

The dataset will never grow beyond 2,000 rows

There is no way to write a delegation-friendly formula

---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."
Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

@mdevaney Thank you for your prompt response. I got your point. So I am getting this delegation warning at around 30 places inside my app.

The following are 3 sample formulae where I am facing the same delegation warning.

ClearCollect(CoordinatorMatrixTemp,AddColumns(CoordinatorMatrix,
        "LookupField",Site &"-"& IWorkFor &"-"& Attribute,
        "Coordinator1",First(Filter(CoordinatorList,CoordinatorList[@Value] = CoordinatorMatrix[@Value])).Coordinator1,
        "Coordinator2",First(Filter(CoordinatorList,CoordinatorList[@Value] = CoordinatorMatrix[@Value])).Coordinator2,
    )),

ClearCollect(
        MyAssignments1,Filter(Resource_database,
        Office365Users.MyProfile().DisplayName in Resource_TO || Office365Users.MyProfile().DisplayName in Resource_TO2
))

If(!IsEmpty(Search(Filter(Resource_database,ResourceTaskTable.Selected.TaskID in TaskID),Office365Users.MyProfile().DisplayName,
    "Resource_AQE","Resource_AQE2","Resource_AQE3","Resource_AQE4","Resource_AQE5"
)),true,false)

My records can easily cross the 2000 mark and might even reach 10,000. Could you please suggest the best approach to avoid any error caused by this delegation warning? I will accordingly replicate it in all places in my app where this warning is visible.

Regards,
Aakash