Unanswered

Get a row couldn't find the right value

(0) Share

Report

Posted on by Martijn2

Goodmorning all,

I am working on a flow that looks up daily whether a date in an excel file is older than 3 years. So it looks for a date in the rows of a column. This is what the excel file looks like:

Using format date time and a pasttime construction, it arrives at the date 3 years ago. This flow runs every day. Only succeeds with the get a row file that should extract the information from these cells that is older than 3 years to find this date. Could it be that it is a different data type or influenced by the cell properties?

"No row was found with Id '28-3-2021' It does not find the queue while it is actually there.

Thank in advance

Categories:

General topics

I have the same question (0)

All responses (5)

Answers (3)

Verified answer

creativeopinion 10,502 Super User 2025 Season 2 on at

Like (1)

Report

@Martijn2 The Get a Row column requires a key column and key value. The values stored in the key column must be unique. Using a Date as a key column will produce unexpected results as the values may not be unique.

You will need to use a List Rows Present in a Table action. This action will return all rows from the selected Excel Table.

Hope this helps!

If I helped you solve your problem—please mark my post as a solution ✅.
Consider giving me a 👍 if you liked my response!

👉 Level up your Power Automate skills by checking out my tutorials on YouTube
👉 Tips and Tricks on TikTok and Instagram

Was this reply helpful? Yes No
Chriddle 8,436 Super User 2025 Season 2 on at

Like (1)

Report

A date can certainly be unique ‌‌😉
The problem here is that Excel internally stores dates differently.

Was this reply helpful? Yes No
creativeopinion 10,502 Super User 2025 Season 2 on at

Like (1)

Report

@Chriddle I suppose but if there are a few rows with the same date would that not cause an issue with the Get a Row action?

Was this reply helpful? Yes No
Verified answer

Chriddle 8,436 Super User 2025 Season 2 on at

Like (1)

Report

Probably, but even if this isn't the case, the approach of the OP does not work.

In Excel, a date is a number, not a date string as in Power Automate.

Therefore the date string has to be converted to such a number in order to act as a Key Value.

I wouldn't go that path and I also recommend using "List rows" with an odata filter.

Was this reply helpful? Yes No
Verified answer

Martijn2 77 on at

Like (0)

Report

Hi all,
Thanks for your responses.

I found a workaround to make it work in my situation. The problem was with the dashes and the format. Since there is in my case also a flow that adds the dates in this cell. I was able to add a json() function that puts the date in a json format and a replace function that removes the dashes. Then it does recognize this. Basically, it is then findable for the get a row action.

Was this reply helpful? Yes No