2000 Row Limit - even with Dataverse?

[jed76]

Hi

Before I get carried away with Dataverse tables, can anyone confirm that the 2000 row limit still applies with Dataverse tables the same way as it does for SP lists etc., or is there no limit?

Many thanks, Justin 

[iAm_ManCat · Accepted solution]

Hey @jed76 

The limit only applies if you are using a function that is non-delegable for that datasource

(or if you are trying to collect records locally in the app, in which case the upper limit is set per batch action by Power Apps settings rather than by datasource, however you can collect these multiple times in separate batches if you Must have that many records locally, although there are usually better ways of doing this)

Delegation documentation is here

And delegation details for the Dataverse datasource are here

Cheers,

Sancho

[jed76]

Aah - so I can pull more than 2000 rows if I am using a delegable function?

[iAm_ManCat]

If by pull, you mean Collect, then No, not pull. but if you mean 'have the datasource deal with it' then yes.

You can use one of the delegable commands to enact that function on the server side, that is what delegation means - it delegates the action to the datasource, instead of doing it locally on your device.

So let's say I only want to show items where Column1="Yes"

If I use a non-delegable function or operator, like Filter(DatasourceName, "Yes" in Column1)

Then the gallery would get the first 2000 rows, bring them into your device to be dealt with locally, then filter that 2000 by the Column1="Yes" condition - let's say there's only one item in the first 2000 records that matches that and all of the others are in rows 2001 to 3000 - you will only see one record in the gallery.

If I have the following in a gallery Filter(DatasourceName, Column1="Yes")

- the request to filter is then sent (delegated) to SharePoint/whateverDatasource and it returns you the data that has been filtered, This means I will see not only that one row that appears in 0 to 2000 but also all of the other rows that appear in 2001 to 3000 as the filtered data is sent back as a response.

[jed76]

That's what I thought but what if I have more than 2000 rows which I want to show in the gallery?

[mmollet]

https://www.youtube.com/watch?v=EdwqaBgBSTY&t=864s

I have galleries that are showing much more than 2000 items. The above video show 5x the limit in a gallery. Again its all about delegation really.

[jed76]

Yes I see - I've seen this before. So basically there is no way to directly show more than 2000 items in the gallery from the datasource without adding items to multiple collections and then combining the multiple collections into one new collection? 

[iAm_ManCat]

If you have a delegable formula, then more than 2000 rows are available, it will handle the paging for you if it can access them, for example, I have a massive list that I use for testing this:

Here I scrolled down from row 1 to over 2000

Then scrolled down further, all the way past 4000 records:

As long as your formula is delegable, the gallery will handle the paging requests to the datasource and get them in batches of like 200ish per additional scroll

[jed76]

Great. So is it better to use a delegable function directly from the datasource to show more than 2000 rows rather than using multiple collections? Many thanks. 

[mmollet · Accepted solution]

Def easier to keep track of rows. Once you start batching 2000 here and 2000 there and 2000 in another place you can easily get lost and mess something up. If you have all the data you need right there in one gallery the app will function much more smoothly.