Excel Limit - Flow stops processing at row 47

(0) Share

Report

Posted on by lardo5150 Microsoft Employee

I getting a list of rows from a table.

My table has 53 rows, about 26 columns.

What I am doing is for each row, I take the column data, and move it over 1.

For example, Row 1, I take column value from column 2 and put it in 1.

Take 3 and put it in 2, etc.. all the way up to 22.

The flow is not failing, but I am finding values starting at row 47 are not moving. This makes me think I am hitting a limit, but not sure which. I only have 53 rows, so not hitting the default row of 256.

Since I am doing so much data manipulation, maybe an API call?

I am going to break it up by using an increment integer variable, but does anyone have any idea what I am hitting?

Categories:

General topics

All responses (3)

Answers (0)

Sort by

CFernandes 8,504 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Hey @lardo5150

I assume you might have tried the Pagination and give it a try although I think its not related -

I assume you are going to try the below - this from the thread - https://powerusers.microsoft.com/t5/General-Power-Automate/How-to-get-more-than-256-rows-from-excel-using-Pagination-in/td-p/595774

Create a variable varRowCount and set the value to 0.

In the List rows present in a table action, set Skip count to varRowCount.

Use Do Until loop repeat the batches. In every iteration, increase the varRowCount value by 250. You can read any number of rows with this approach.

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!
lardo5150 Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

I have not tried that, but will try it. I thought that was for only rows?
I only have 53 rows, but I am doing a ton of manipulation in the update row connector.

can you explain that approach a bit more?
Why are we increasing by 250 and not just by 1?
I am waiting for the Service Incident to resolve so I can hop in and try and set this up.
lardo5150 Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

ok, I think I know what is happening here.
We set it to zero for the first batch.
Then we set it, for my case if I want to split it up in half, to 25.
It will then come in the second batch, skip those 25 it has already done, and pick up after that?