Question

A developer builds an external .NET service that uses the Dataverse Web API to export all rows from an 'account' table containing over 500,000 records. The first request returns exactly 5,000 rows plus an '@odata.nextLink' property, even though no $top was specified. The developer needs to retrieve every record efficiently while minimizing round trips. What is the correct approach to page through the entire result set?

Accepted Answer

Follow the '@odata.nextLink' URL returned in each response until no nextLink is present, sending each request as-is without modifying the URL.

Answer

Add '$top=500000' to the original query to override the default page size and return all rows in a single response.

Answer

Append '$skip=5000' to the original query and repeatedly increase the skip value by 5,000 until an empty result set is returned.

Answer

Set the 'Prefer: odata.maxpagesize=500000' header once and re-issue the same query to disable server-side paging.