Logic App Dataverse Connector FetchXML will not return more than 512 records

Question

Logic App Dataverse Connector FetchXML will not return more than 512 records

Scott Brownhill 10

Hi All, got issue where Dataverse connector will not return more than 512 records when using FetchXML. Have tried using the paging settings of the connector and top property of FetchXML (and combinations of both). I converted the FetchXML to web api call and it retuned more than 512 (expected result). I do notice that at some stage between 2am 29th Jan and 2am 30th Jan (NZ time) the "Preference-Applied" header of the Dataverse connector response started including "odata.maxpagesize=512". I assume this was a Microsoft update to the connector. Thought I would ask if anyone else is experiencing this and knows what to change or if there is a setting on our Dataverse tenant that may need to changed. Any assistance would be much appreciated. Thanks

1 answer

Your answer

Answer 1

Khadeer Ali 4,235 Microsoft External Staff

@Scott Brownhill ,

Welcome to Microsoft Q&A Platform!

Thanks for reaching out. Looks like the Dataverse connector is capping at 512 records with FetchXML due to paging settings and connector limits. The docs say the default and max page size is 5,000 rows, but if you see "odata.maxpagesize=512" in the "Preference-Applied" header, it means the connector is set to limit records per request.

Try these steps to fix it:

Check Connector Settings: Make sure there are no tenant-level settings in your Dataverse that are enforcing this limit.
Use Paging Cookies: Instead of just using the top property or paging settings, try using paging cookies to handle larger datasets.
Monitor for Updates: Keep an eye out for any Microsoft updates or documentation changes about the Dataverse connector that could affect paging.

References:

Hope this helps. Do let us know if you have any further queries.

If this answers your query, do click Accept Answer and Yes for "Was this answer helpful." And if you have any further questions, let us know.

Scott Brownhill 10 Reputation points

2025-02-10T20:34:31.7166667+00:00

Further to this, the FetchXML query execution is also ignoring the "top" and "count" options when included in the FetchXML query to restrict the number of records returned (e.g. top="1" or count="1"). Just continues to return 512 records. If I run the exact same FetchXML using SDK it limits the number of returned records.
Scott Brownhill 10 Reputation points

2025-02-10T21:18:15.3933333+00:00

Same FetchXML run in Power Automate returned 1 record when using "count=1" and returned all records when "count" was omitted (1155 records returned).

I notice that in Power Automate the "Preference-Applied" header does not have "odata.maxpagesize=512" included.

Something wrong with the Dataverse connector for Logic Apps.
Linus Hovland Udén 5 Reputation points

2025-02-11T09:18:43.9166667+00:00

I have also noticed the same problem, we had to switch several flows over to power automate
Khadeer Ali 4,235 Reputation points Microsoft External Staff

2025-02-12T11:54:02.65+00:00

I will check with internal team once and get back to you on this.
Roberto Ilidio 0 Reputation points Microsoft Employee

2025-02-17T09:56:53.39+00:00

There was a change in the Dataverse Connector for Logic Apps. Due to performance reasons, the new records-per-page limit when using pagination is now set to "odata.maxpagesize=512.". it is a change applied by Microsoft and can not be customized.
Ivan Secci 5 Reputation points

2025-02-24T11:43:05.6633333+00:00

This is also affecting paging. Since the change, the paging cookie has been returning the same value each time, causing all our loops to cycle indefinitely.

Share via

Logic App Dataverse Connector FetchXML will not return more than 512 records

1 answer

Your answer