I am trying to update a cell in in an excel file but my flow keeps returning 404 error unable to find the the row with ID....
Here is the flow:
SubString FYI: substring(body('Get_file_metadata')?['Name'],0,11)
I have also tried just using the folder name as the Key Value, but still no luck.
It keeps falling over at 'Update a row', here is the output:
As you can see it's there in A:5...
Thanks in advance.
the bug is definitely not fixed.
And the Compose workaround doesn't work for me.
The rows are simple (unique) Integers in the source as well as in the target table.
Get a row also returns the same 404, with or without the use of a compose
The row headings are integers or the values? If it is the heading the issue may be that it is looking for a string and checking from an integer, in which case you should cast them both to a string or integer because '5000' is not equal to 5000
Asuming that it is somehow related to the fact that the key column contains numbers and Power automate flows are quite alergic to integers, i devised a workaround, which is not very elegant, but does the job.
I added an extra column to the tables, where i automatically added a character preceding the original key columns content.
So basically the original column says 638 and now the added column says D638.
Of course i Needed to add this in both tables.
Using this column and value to update rows seems to work now (at least it worked a couple of times).
What makes this bug maddening is that it's not consistent. Sometimes it works. Sometimes it doesn't for the same exact worksheet. It's not idempotent.
Another issue is that it doesn't matter what the nature of the data is e.g. int or string. It just doesn't work.
Yet another issue is that even something as basic as GetRow(i) or DeleteRow(i), where i is the row index number, also doesn't consistently work.
Until Microsoft finally decides to fully fix this bug (it's been years now), Salesforce is going to remain the market leader for low code platforms.
the robustness of flow code in general is rather dissapointing indeed.
Being marketed as a professional solution, this is getting implemented in business processes.
But in fact it is still far too unstable and unreliable for that.
The word "Power" should be placed between brackets.
This is related to the issue "404 error unable to find the the row with ID", But not the exact scenario as mentioned by the Thread initiator.
If you have unchecked the Header Row check box under table design tab, this issue happens for 1st row.
As a workaround I enabled the header and kept the header text as same color as column name.
I made a ticket with MS and we found a way to fix it. @MattMack In my scenario I placed a 2 min delay between trigger and the action. But depending on your scenario your solution might be different.
@ Shavora, great and good to know. Will try that if run into problems again. I ended up fixing by copying the table and pasting only values in a new workbook and then creating a new table again from scratch which seemed to do the trick. What's odd is I triple checked the formatting of the key value column to ensure it matched the item I was searching for but still received error. Not sure what other formatting in the table was causing the problem but the overall table formatting seems to be an important part of getting this to work.
I don't know what the underlying reason behind the problem is.
But indeed, completely replacing columns or even the entire table usually solves the problem too.
This my be related to the row that you are querying having duplicate values or empty rows, even if the one that you are querying is not duplicated.
I had the same issue because the table was selecting additional empty rows at the end but once scoped the table properly the excel update a row start working correctly.
Don't know if this applies to your flow but this worked for me. Just posted the same answer in another thread as well. Read below:
I had problems with updating a row as well, got it to work. I had two different tables created in Excel, one was working the other was not.
Short answer: Name your table columns starting with letters and the error is not related to your key column, but the whole table.
I concluded that the way the actual tables in Excel were created did not matter. Thought it might be a bug from Excel depending on how the table was created. Can be created by:
1. Creating a table from table/table range.
2. Creating a table by inserting a table.
(Also tried some other far fetched theories in Excel here)
I concluded that it had nothing to do with the data in the table as my two tables had the same data in the tables (again, one was working and the other one wasn't).
I concluded that integers in the key-column do not matter.
Integers stored as general/text/number works fine:
All my values in the key column were numbers. I then tried changed the cell settings on the table where it was working to all three, all were fine.
I then tried changing the name of my columns. Note that column A (ManagerId) is the key column.
(No updates in the table here as PA crashed. I was trying to populate columns ManagerName,1,2,3 and 4)
(Data is updated in columns)
When I got it to work using letters to start my column names...
...I changed the columns back to numbers within the exact same table it crashed again. I had made no other differences to Power Automate, Excel, table in Excel or the data in the table.
Just wanted to update this thread since I faced this issue recently. I had used a 'get a row' excel connector which resulted in the No row with ID error. While studying the excel data source, I found that the excel sheet table range was not correct even when there were additional rows.
Go to Table Design --> Resize Table (Should be the one in the Properties menu in the ribbon) and verify the table range.
After resizing the table. It worked!
Keep up to date with current events and community announcements in the Power Automate community.
A great place where you can stay up to date with community calls and interact with the speakers.
Check out the latest Community Blog from the community!