The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Most of the "get" actions in Power Automate use pagination, meaning they return the first 500 rows by default, then stop. If you want them to return more, go in the settings for the step that gets the data and enable pagination, then set the threshold to above the maximum number of rows you expect to need to get.
@christinepayton - Thank you for your response. I have not used Get actions in my flow and I do not fine a step which as "Pagination" in my flow. Can you please provide details of which step I should be changing from my flow below.
How many columns are you querying? The limit on the "run a query against a dataset" is 1million values, with values = rows x columns. If you have a lot of columns, I would reduce the number. But also try running a length() expressionon the "run a query" output in a compose action to see how many rows the output has for that action specifically - that will tell you if you if the issue is that step or another step.
@christinepayton - The output has 21 columns in total and currently we have 46398 rows in Power BI.
If you've just copied the code straight from the performance panel, remove the section at the end that starts with TOPN(501...) and update the evaluate part accordingly.
@vicky_ - thank you for your response. Yes, I was using the code directly from Performance analyser. I removed the TOP N and now it brings 28k rows which is still not matching Power BI output which has 50k rows. Can you advise ?