Unanswered

Delegation limit and Collection size

(0) Share

Report

Posted on by oguruma

I don't quite understand the limits of delegation and collection sizes.

I have a custom connector that I made. I set the App to load all records (about 600 from the development environment) into a Collection when it starts. It loaded the records without any errors or warnings, even though I set the "Limit number of records" setting to 100 (as a test).

I thought, "oh, it must not actually be loading all of those into the App." However, when I use Monitor, and load the same records into a Collection, it does show the amount of data transferred as about 1MB, which is what I'd expect based on the number of columns.

If Powerapps has a maximum collection size of 500 (by default), how am I able to load all 600+ records into a Collection?

Categories:

Building Power Apps

I have the same question (0)

All responses (5)

Answers (0)

Ramole Super User 2024 Season 1 on at

Like (0)

Report

@oguruma
How many rows is set in PowerApps setting? you push to 2000

Was this reply helpful? Yes No
oguruma 48 on at

Like (0)

Report

Right, but I've specifically set it to 100, and yet the ClearCollect (colMyCollection, MyAPI.Get600records...) actually seems to load all 600 records...

For example, if I set a Gallery to have a data source of colMyCollectionOf600Records, I can use Filter() and Search() to grab row # 600 without any problems..

Was this reply helpful? Yes No
RandyHayes 76,297 Super User 2024 Season 1 on at

Like (0)

Report

@oguruma

Collections are tables that have NO limit to their size. The size of a collection is only limited by the amount of memory you have.

Record Limit is another story - record limit will determine the maximum number of records you can retrieve in a data operation. The Maximum is 2000.

Delegation is something totally different. Delegation is the ability to delegate a query to the datasource. However, even when delegated, the maximum number of results returned is governed by the record limit. You can never exceed that.

I hope this is helpful for you.

Was this reply helpful? Yes No
oguruma 48 on at

Like (0)

Report

Is the Record Limit different than the "Data Row Limit" that's available in Settings?

As an example, I've set that to 50, and I still have a gallery that will show me all 600+ records from a Datasource.

Is that because Powerapps is able to only load the records that I can actually see in the visible pane of the Gallery (and thus is not actually loading the entire 600+ rows at any given time)?

Was this reply helpful? Yes No
adedapo 256 on at

Like (0)

Report

I know this is over one year but it is always a good thing to clarify what the data row limit is.

The first thing to know is that it is not called the delegation limit but rather it is the data row limit. However, the description in Power Apps refers to this limit as a limit that applies to non-delegable queries to the standard data sources. This is not actually acurrate. As @RandyHayes correctly points out, it is applied to the standard data sources, regardless of if the query is delegable or not.

The exceptions are galleries and data tabels which apply their own limit (and therefore ignores the data row limit) and also performs pagination under certain circumstances (i.e delegable queries without additional functions). Outside of these very narrow constraints, they behave like other controls and queries--even delegable ones--are restricted by the data row limit.

As for your particular case, since your data source is from a custom connector, you are responsible for the request limits and the data row limit does not apply.

Was this reply helpful? Yes No