Delegation errors on collections?!

(0) Share

Report

Posted on by EpicTriffid

364

Hi there,

So in order to bypass delegation, I have used a collections to house my lookup lists and datasets. However, I just looked on the monitor, and I'm getting a massive amount of delegation warnings where I have used that collected, all with the same message:

"This function can be delegated but the selection formula used prevented the datasource from processing the query.It might not work correctly on large data sets and an incorrect result might be returned.The data row limit for non-delegable queries defined in the app settings is 2000."

I was under the impression this wouldn't occur when using un-delegable formulas against a collection. As far as im aware, I'm not even interacting with the raw datasource, only the collection! Any help?

Categories:

Building Power Apps

I have the same question (0)

All responses (4)

Answers (1)

eka24 20,923 on at

Like (0)

Report
Copy link

Link copied!

Can you show the code that is giving the error?

------------

If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users find it.

Was this reply helpful? Yes No
EpicTriffid 364 on at

Like (0)

Report
Copy link

Link copied!
Both

If( CountRows(wlmSupervisors) = 1, 40, CountRows(wlmSupervisors) = 2, 70, CountRows(wlmSupervisors) > 12, 349, CountRows(wlmSupervisors) * 32 + 10)
and
LookUp(supportRoles,Role='Role Dd_1'.SelectedText.Value,Max_x0020_Hours) * staffSelected.FTE

give me the error about being non delegable despite them operating on collections.

Was this reply helpful? Yes No
EpicTriffid 364 on at

Like (0)

Report
Copy link

Link copied!

Can anyone help with this? Its becoming quite a problem

Was this reply helpful? Yes No
Verified answer

EpicTriffid 364 on at

Like (0)

Report
Copy link

Link copied!

I have resolved this. I was saving my lists to variables rather than collection, so the function wasn't being delegated. I change "SET" to "CLEARCOLLECT" and this has solved the problem. My mistake.

Was this reply helpful? Yes No