web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Filter Array Connector...
Power Automate
Suggested Answer

Filter Array Connector Limitation on number of rows being filtered

(0) ShareShare
ReportReport
Posted on by 6
Overview
List Rows is filtering a set of data from a Dataverse table and returns 500k+ records. 
The filter query is then executing another set of filter criteria on the data that comes out of the List Rows connector.
 
The issue is, there are a number of items which are added to this table based upon popularity of a users selection. Thereby the data exceeds 500k+ for particular items. 
These items go through the filter query and despite the filter being correct, the output is always an empty array. This results in me returning an error message to the user which is incorrect.
 
I have tracked the record based off the filter criteria manually through the tables and the records exist. But the filter still doesn't work.
 
Data is continuously added everyday and now the number of items this is happening to is increasing as time passes.
 
I have opened a microsoft ticket but the response hasnt been as helpful as I expected and has taken a month with not much response from them.
 
I have 2 questions:
- Does the filter query connector have a throttling limit? as I havent found any documentation to suggest this is the case
- If the above is true and there is a throttling limit, would archiving or deactivating records retrieve less datarows when listing/filtering?
- Has anyone else experienced this issue and come to a resolution?
 
To note:
- I cannot provide the data examples as the data is sensitive
- I did not build this flow or application so my response to questions asked may take a bit longer if I dont have the immediate answer
 
 
Categories:
I have the same question (0)
  • Suggested answer
    David_MA Profile Picture
    12,982 Super User 2025 Season 2 on at
    The default is 5,000 rows. By enabling pagination, you can get up to 100,000 rows. This article explains how to get even more if needed: Power Automate | How to Get More Than 100,000 Rows From a Dataverse Table - Encore Business Solutions. It also shows you how to enable pagination. I recently needed to use the @odata.nextLink method for an HTTP request to the graph API and it worked great.

    And if it comes in handy, here is how it is used for a HTTP get request against the Graph API: Paging Microsoft Graph data in your app - Microsoft Graph | Microsoft Learn
  • LA07K1 Profile Picture
    6 on at
    Hey David, 
     
    Thanks for your response ,
     
    The List rows output is correct and returns the expected value,
    But in specific cases, lets say with 1000 records passing through the filter. Despite the record existing in the List Rows output the filter outputs an empty array.
     
    The filter seems to not work rather than the filter query within List Rows. I hope that makes sense!
     
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 501 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 323 Moderator

#3
abm abm Profile Picture

abm abm 237 Most Valuable Professional

Last 30 days Overall leaderboard