Unanswered

Run a query against a dataset doesn't show all data

(1) Share

Report

Posted on by Emily_Pollard

Hello All,

I am using the 'Run a query against a dataset' connector, and last week I was able to get all 67,000 rows (10 columns) back using this connector, however when using it now this week I am only able to get 58,000 rows (roughly 10,000 less than before) no matter what I do. The connector obviously is able to bring the amount of rows I need back, but I am not able to figure out how to get it to work again. I have tried creating another flow similar to this, I have tested that the query and it shows that the number of rows is correct, it just doesn't seem to work when entered into power automate.

Has anyone else experienced this and if so how did you fix it. I need all rows to come back at once and to my knowledge I am not hitting any limits.

Please help!

Emily Pollard

Categories:

Using connectors

I have the same question (0)

All responses (10)

Answers (0)

lkkkhgg 9 on at

Like (0)

Report

I have the exact same issue in multiple flows, I have no idea what is causing this

Was this reply helpful? Yes No
JegErAlan 4 on at

Like (0)

Report

Best I can tell is that there is some total data limit in the "Run a query against a dataset" call. If I add more columns (more data), I get less rows. I've been searching, but I haven't seen any documentation that speaks to the limit, whether it can be changed, etc.

I even looked at the raw JSON output of the query step, and its records were limited. (That is, in my case, it wasn't the "Create CSV table" next step that was causing the limit.)

Was this reply helpful? Yes No
lkkkhgg 9 on at

Like (1)

Report

we fixed it, check out this video:

Export MORE THAN 100k rows of Power BI data to CSV using Power Automate | No ROW limits! - Bing video

Was this reply helpful? Yes No
JegErAlan 4 on at

Like (0)

Report

Thanks. I saw that work-around, and planned on using it if folks still want the larger dump. Seemed a lot of hoops to jump through.

But thanks for the response!

Was this reply helpful? Yes No
rsalam 8 on at

Like (0)

Report

Do you have measure column? If so you have to define the measure when running the query.

Was this reply helpful? Yes No
Rimelflash 4 on at

Like (0)

Report

I think this video solves grabbing rows more than 100K. It seems possible if we have less columns (5-15). But if we have more than 50/60 columns than 'Run a Query against dataset' does not show all the rows. I have a dataset around 5000 rows, If I add all the columns (more than 50), I only get 2227 rows.

Was this reply helpful? Yes No
lkkkhgg 9 on at

Like (0)

Report

It works regardless of the amount of column, but you may need to reduce the batch size. In your case, a batch size of 2000 rows would work.

Was this reply helpful? Yes No
Rimelflash 4 on at

Like (0)

Report

Thanks, Now it works. After limiting the batch size 2000 rows, now it is able to grab all the columns.

Was this reply helpful? Yes No
pmohno 5 on at

Like (0)

Report

How did you limit the batch size? Was it in query itself or through power automate flow?

Was this reply helpful? Yes No
KC-05022245-0 2 on at

Like (0)

Report

I think it is the Actions Per Workflow limit discussed HERE. The limit is 500 and that's what I run into. Output from Run a query against a dataset just stops at 500. Seems ridiculously low to me. I'm still searching for a way to deal with this.

Was this reply helpful? Yes No