Azure / Azure/logicapps

Dataverse FetchXml "top" parameter suddenly ignored. 2000 records are returning by default.

Open
#1,388 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
ABAP
Stars
424
Forks
320
Avg merge
14h 41m
Merged PRs (30d)
1

Description

### Describe the Bug with repro steps

In several production Logic App (Standard) workflows, we have a Dataverse FetchXml statement with a "top" parameter that specifies the number of records to return for the query. Starting sometime on 3/17/2025, the Dataverse connector or Logic Apps runtime is removing or otherwise ignoring the "top" parameter and this results in the query returning 2,000 records for each run. The quick fix was to provide a value for the action's Row Count parameter. But the sudden change in functionality is causing problems.

Example: The following FetchXml statement in a "List rows" Dataverse action now returns 2,000 rows instead of the expected 50:

### What type of Logic App Is this happening in?

Standard (Portal)

### Which operating system are you using?

Windows

### Did you refer to the TSG before filing this issue? [https://aka.ms/lauxtsg]()

Yes

### Workflow JSON

```json

```

### Screenshots or Videos

*No response*

### Browser

Chrome

### Additional context

*No response*

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.