Unanswered

Dataverse exceeding 2000 rows

(4) Share

Report

Posted on by sasrsc

678

This is specific to DV.
I am needing to create collections in my Power Apps and I'm finding that for larger events I'm exceeding the 2000 row threshold.
My workaround is to use the Power Automate, List Rows with Pagination and use the Response action to bring data back.
Here's the "headscratching moment" and the later "aha" moment.

My row counts are dynamic and my Dataverse tables have parent/child relationships and Power Apps is great about honoring those with the filter functions, etc... so I can get values from multiple tables.

But by default, the Power Automate workaround above is a single table. That makes it extremely hard to bring in data from multiple tables and build out the relationships if you ultimately want to query from parent, child tables, etc..

The aha moment - comes when I realize I can use FetchXML to achieve this pulling in data from multiple tables in one ListRows action in Power Automate.

I want to see if I'm on the right track here and FetchXML is the ideal answer to this when you need to pull in data exceeding 2000 rows from DV from multiple tables for the creation of collections?
True/False?

If there a better method?

I feel like the rabbit hole keeps getting deeper and deeper.

Categories:

Building Power Apps

I have the same question (0)

All responses (4)

Answers (0)

Pstork1 68,717 Most Valuable Professional on at

Like (1)

Report

In general its best not to retrieve all the data at one time into the App. You'll get better performance overall and less data corruption if you leave the data in Dataverse and use filtering and searching in the app to retrieve the information that the user needs to work on right now. So I would suggest rather than looking for another way to retrieve all the data at one time, redesign the app to only retrieve necessary data when the user needs it. Why do you need all the data in the app at once?

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No
stampcoin 5,058 Super User 2025 Season 2 on at

Like (1)

Report

sasrsc , Hi,

Myself l perfer to use API + Odata paging, or use Azure function/logic app.

depends one how the end user interact witht the data ,and where they located.

Was this reply helpful? Yes No
sasrsc 678 on at

Like (0)

Report

I plan to experiment with the low code plugins and see if that could answer my needs and therefore I absolutely could keep the data in DV and just filter on the fly. My issue pertained to setting values based on the children rows which is why I was needing to pull in data proactively, otherwise you both are totally correct. The strategy of "don't consume it unless you need to".

I didn't explain the full use case.

I have used the API action with paging and that is cool.
So far pagination doesn't seem to be working with my List Rows action (I turned it on) so I'll try the same thing but in a HTTP action to see if I can get it working. I'm wondering if the pagination doesn't work with List Rows when you're using fetch xml?

Was this reply helpful? Yes No
enriqueglopez 503 Moderator on at

Like (1)

Report

Why do you need that much records? You could use filters or search when needed, that will made the application faster and more optimized.

Was this reply helpful? Yes No