Unanswered

Power Automate not reading date row correctly

(2) Share

Report

Posted on by powcontributer3

I have an excel sheet automatically being uploaded from outlook to my SharePoint folder everyday. Within the excel sheet, the date column reads as a custom number format. When building out the flow, I selected ISO 8601 within the read rows action and nothing seems to work, my outputs for the date column still reads as serial numbers. Any insight on what the issue could be?

Categories:

Building flows

I have the same question (0)

All responses (5)

Answers (1)

lbendlin 8,474 Super User 2025 Season 2 on at

Like (1)

Report

Does it really matter? That looks like a good date integer. You can convert it back to whatever format you need.

Was this reply helpful? Yes No
Verified answer

v-yetonggu-msft on at

Like (1)

Report
Hi @powcontributer3 ,
Do you want to know why the custom number format of the date column in Excel cannot be converted to ISO 8601?
Because the ISO 8601 format is a date conversion format suitable for date and time types in excel, custom number type cannot be converted.
If you want to convert to ISO 8601 format, I have a test for your reference.
In my scenario:

addDays('1899-12-31',int(items('Apply_to_each')['date']),'yyyy-MM-dd')

Best Regards,
Sunshine Gu

Was this reply helpful? Yes No
powcontributer3 43 on at

Like (1)

Report

Thank you so much. Your input as been very helpful. I think I am getting closer to figuring this out

I do get this error,

Unable to process template language expressions in action 'Compose_2' inputs at line '0' and column '0': 'The template language function 'int' was invoked with a parameter that is not valid. The value cannot be converted to the target type.'.

As I review the outputs from list rows, it seems there are two values within Column5 that are not numerical. It seems these are in the first two rows. Maybe this is the reason. Can I bypass this?

Was this reply helpful? Yes No
powcontributer3 43 on at

Like (1)

Report

.

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

Like (1)

Report

same here, I think it's a bug, don't know why MS don't fix this!

Was this reply helpful? Yes No