Unanswered

No row was found with Id

(2) Share

Report

Posted on by Simoyes

Hi I have a flow that pulls data from a planner and updates an excel sheet.

I pickup the original id for my excel Key by adding the planner task to the excel row and populate my key column with the planner task id

However I seem to be getting intermittent results. Reviewing a run I can see that I am receiving:

"No row was found with Id" where the Id actually matches a key in my excel sheet.

I have 393 rows in my table currently all populated from planner.

I use a List Tasks to pickup the tasks from planner,

I then use an apply to each containing a get a row, which compares the planner task id against the excel row key

If they match it updates the rows, if the do not match then it adds a new row.

Why is the planner id not always matching? When it is directly populated from planner?

Any help or advice would be greatly appreciated.

Best regards

Categories:

General topics

All responses (25)

Answers (0)

Sort by

jinivthakkar 4,187 on at

Like
a
(0)

Report
Copy link

Link copied!

@Simoyes don't understand but I will try to answer this, the mismatch could be because of the array structure, the array index starts with 0, so your first element is available at 0 index, and if you compare it with something that starts with 1, then it would always mismatch.

So in array you could 393 rows but array index would be 0 to 392.

--------------------------------------------------------------------------------

If this post helps answer your question, please click on “Accept as Solution” to help other members find it more quickly. If you thought this post was helpful, please give it a Thumbs Up.
Simoyes 14 on at

Like
a
(0)

Report
Copy link

Link copied!

@jinivthakkar ,
thank you for your response, as you can see from the image below, the match is done by mapping the id to the key, so I wouldn't have though the array would be causing intermittent issues
jinivthakkar 4,187 on at

Like
a
(0)

Report
Copy link

Link copied!

@Simoyes so you are getting error at "Get a row" action ?
Simoyes 14 on at

Like
a
(0)

Report
Copy link

Link copied!

@jinivthakkar,
I get the error "No row was found with Id" in the update a row action. Which is after the condition check.
Laetoune 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi,

I have exactly the same issue. Is it a bug ? Did you solve it ?
The message says Id and not ID in caps whereas my field in Key Column is in caps

My excel: ID 1 exist

Many thanks
Simoyes 14 on at

Like
a
(2)

Report
Copy link

Link copied!

No, I haven't found a solution to this. It happens intermittently to me. It appears to be one of those issues that no one quite understands. Any experts out there have any further ideas?
RaeandKhali 12 on at

Like
a
(1)

Report
Copy link

Link copied!

I have run into this issue myself, sometimes it works, sometimes it does not.

My flow is getting response details from MS Forms, and then based on the response, updating an Excel spreadsheet that tracks the responses that people have submitted. Of course, when it doesn't work, the tracking becomes obsolete, because the same submission will not happen again. I then have to go in and manually update the tracking for 30 different spreadsheets.

Does anyone have a workaround?
MattMack 43 on at

Like
a
(3)

Report
Copy link

Link copied!

@microsoft I've browsed multiple forums on this topic and have yet to find an answer that works. Same issue as above. Can you please advise or help us with fixing?
RaeandKhali 12 on at

Like
a
(0)

Report
Copy link

Link copied!

What ended up being the problem for me was the source string had non-breaking spaces that were interfering with the match. I had to substitute non-breaking spaces & remove all spaces to get it to work. Sorry if I can't articulate it with the correct terms, but hopefully that's logical!
rxbpherrera 2 on at

Like
a
(0)

Report
Copy link

Link copied!

My source data is from another excel file. How did you find the non-breaking spaces on your data? I have a feeling it's something easily fixable but it would be tough for me to go through 516 rows of data to find it.