Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Power Automate - Building Flows
Unanswered

Adjusting 1000 row limit on dynamic content passed from Power BI to Power Automate

(0) ShareShare
ReportReport
Posted on by
Is there a way to increase the 1000 row limit on dynamic content passed from Power BI to Power Automate?
 
I have a button in my Power BI report that triggers a flow using the "On PowerBI Button Clicked" trigger. I pass a set of columns from that report's semantic model to flow by adding those columns to the button in the report, and then collect those within Power Automate via dynamic content, but I am limited to 1000 rows. Setting aside the row limitation, this is an ideal solution, because it allows me to pass data through based on the columns selected in Power BI, and the data will automatically be filtered with the page and report level filters active in Power BI.
 
As far as I'm aware, the only alternative available to me is to collect the data via the PowerBI API step "Run a query against a dataset" in my flow, but in order to achieve my goals I would need to create a process of significant complexity. It would require me to implement the following steps for each table in my semantic model: 1) create a measure in Power BI which collects and formats all active filters into a string (which I would pass to flow via dynamic content), 2) develop a method of parsing that string in Power Automate for use in query, 3) develop a method of parsing the columns passed to flow via dynamic content for use in the query. I would then join the results of these queries, and have the desired dataset. If I decided to use this process in another report with a distinct semantic model, I would have to create some hidden measure "key" identifier and pass that through as well, and would also need to repeat step 1 for tables in the new semantic model. There may be detail missing here, but the idea is that this is too complex.
 
None of this would be necessary if the first approach did not have this row limitation--it would just work, no additional processing necessary. I think this alternate solution would likely take me the better part of a week to develop, and will then require some non-trivial amount of maintenance. This is frustrating considering the first solution is so simple and would work perfectly if it weren't for the row limitation.
 
So, is there a way to lift/adjust that row limit? If not, is there any effort from Microsoft to do so?

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

Michael Gernaey – Community Spotlight

We are honored to recognize Michael Gernaey as our June 2025 Community…

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

Leaderboard >