Processing 10,000 Dataverse rows in a single Power Automate List rows action

PL-400 By islever Editorial Last updated

Configure Power Automate cloud flows and Copilot Studio workflows

Short answer

BD Turn on pagination with a 10,000 threshold and follow @odata.nextLink so the List rows action returns all 10,000 records in one run.

Question

You manage a Microsoft Power Automate cloud flow. The cloud flow queries Microsoft Dataverse data by using the List rows action. You need to configure the cloud flow to process 10,000 records in a single run. What should you do? Each correct answer presents a complete solution. NOTE: Each correct selection is worth one point.
  1. Set the row count parameter to 10,000.
  2. Return the first 5,000 records and use the @odata.nextLink in the response to return the remaining records. Correct Answer
  3. Create the query by using FetchXML and set the top parameter to 10,000.
  4. Turn on pagination and set the threshold to 10,000. Correct Answer

Key Takeaways

Pagination is the supported mechanism for retrieving more than 5,000 rows from the List rows action; the threshold tells the connector how many total rows to fetch across pages. The @odata.nextLink is the continuation token the API returns for the remaining pages.

The Dataverse 'List rows' action caps a single page at 5,000 rows. To exceed that in one run you enable pagination and set the threshold to 10,000, and/or rely on the @odata.nextLink the response exposes to page through the remaining records until all 10,000 are retrieved.

Common mistake: Setting 'row count' (A) or FetchXML 'top' (C) to 10,000 directly — both are capped at 5,000, so they silently truncate and never return 10,000 rows in a single page.

Expert Analysis

Why the Answer Is Correct

Option B acknowledges the 5,000-row page limit and uses the @odata.nextLink continuation to retrieve the remaining rows. Option D turns on pagination in the List rows action and sets the threshold to 10,000, which instructs the connector to page through and return up to 10,000 records in the run. Both together meet the goal.

Why the Other Options Are Wrong

Option A (row count = 10,000) is bounded by the 5,000 maximum per page, so it cannot return 10,000 at once. Option C (FetchXML top = 10,000) is also capped at 5,000 for the top parameter, so it truncates. Only B and D handle the >5,000 volume correctly.

Community Comment Notes

pey (likes=5) explains B and D handle large datasets by processing records in batches. 1285cc6 (likes=1) cites Microsoft docs that the maximum top value is 5,000, ruling out C.

Official Reference

https://learn.microsoft.com/en-us/power-automate/dataverse/list-rows

This link opens the official vendor documentation in a new tab.

Community Votes

BD
100%

100% of anonymous learners picked answer BD. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 4 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 4

  1. pey 👍 5
    B & D provide a way to handle large datasets efficiently by processing records in batches, ultimately achieving the goal of processing 10,000 records in a single run.
  2. 1285cc6 👍 1 Answered B
    Max limit for top is 5000, taking from MS docs: https://learn.microsoft.com/en-us/power-apps/developer/data-platform/fetchxml/reference/fetch top No Positive integer value to specify the number of records to return. This value can't exceed 5,000. Don't use top together with the page, count, or returntotalrecordcount attributes. Using OData.nextLink will work for sure. It's all you need.
  3. hai297 👍 1 Answered C
    Should be C https://learn.microsoft.com/en-us/power-automate/dataverse/list-rows?tabs=classic-designer#fetch-xml-query
  4. Juan0414 👍 1
    Correct! B and D

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Diagnosing the 'remote name could not be resolved' 404 for the Northwind Web API connector

S-grade

Solution for Long-Running Transactional Dataverse Operations

S-grade

Why exporting a custom connector directly from the maker portal fails to deploy it

S-grade

Preventing plug-in timeouts when calling a slow external web service

S-grade

Practice All PL-400 Questions

Access 85 questions with complete answers and detailed explanations.

View Full PL-400 Practice Test →

← Back to PL-400 Study Guide