Views:

Applies to Product – Microsoft Dataverse


What’s happening?
The customer is experiencing an issue where the Dataverse action in a logic app workflow is returning more records than anticipated, specifically 512 records, despite applying a Fetch Top filter.


Reason:
Dataverse's backend processes data in blocks of 512 records per "page" for performance optimization. When the FetchXML query is executed with a top setting (e.g., top="45"), the Dataverse connector defaults to a page size of 512 records if no other explicit limits, such as Power Automate pagination settings, are configured. This default behavior results in the connector fetching the first full page of 512 records, overriding the specified top setting.


Possible Resolution:

  1. Review the FetchXML query to ensure that the top setting is correctly applied.
  2. Configure pagination settings in Power Automate to limit the number of records fetched according to the desired criteria.
  3. If necessary, adjust the logic app workflow to account for the default paging behavior of the Dataverse connector.