Answered

SharePoint Dates 8 hour discrepancy

(0) Share

Report

Posted on by KJH1138

Help!

I am running a Flow that copies data from a spreadsheet to a SharePoint list. By manipulating the text in the spreadsheet I am able to generate a string value that can be loaded into a SharePoint Date field.

String generated within Power Automate and stored in a variable: "1/1/1900 12:15 PM"

Result when copied to SharePoint text field: "1/1/1900 12:15 PM"
Result when copied to SharePoint date field: "1/1/1900 4:15 AM"

All of the date fields are - 8 hours from the string that is copied to them. Note: the same string variable is used to populate each field ...

I am perplexed to say the least.

Categories:

General topics

I have the same question (0)

All responses (8)

Answers (1)

KJH1138 53 on at

Like (0)

Report
Copy link

Link copied!

Additional note - when I copy the same string manually the value does not change when I manually paste the string into the Date field -only when it is done via PA

Was this reply helpful? Yes No
v-xiaochen-msft on at

Like (0)

Report
Copy link

Link copied!

Hi @KJH1138 ,

I reproduced your scenario in below test:

You can reshape your string value by this function: addHours(outputsofyourtimestring,8)

So that you will get proper timestamp in date field.

Best Regards,

Wearsky

Was this reply helpful? Yes No
Chriddle 8,515 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

This could be a time zone issue.
When you insert a UTC date string into a date column via Power Automat, SharePoint adjusts it to its local time zone.
If this occurs, don't just add a few hours, set the correct time zone behavior with the convertToUtc(...) function.

Was this reply helpful? Yes No
Chriddle 8,515 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Your life will be much easier if you only use ISO 8601 formatted date strings in Power Automate.
Only format differently if it's really necessary - that hardly ever happens 😉

Was this reply helpful? Yes No
KJH1138 53 on at

Like (0)

Report
Copy link

Link copied!

Agreed - I have been using the ISO 8601 setting up until now but could not get it to work in this particular case due to some creative formatting in the source data which is automatically generated so I'm unable to address the issue at that level.

Was this reply helpful? Yes No
Chriddle 8,515 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!
The parseDateTime() function is your friend here 😉
It's a bit tricky to use, but in the end you can be sure that you'll get a correct date string.
parseDateTime('1/1/1990', 'es-es', 'd/M/yyyy')

Was this reply helpful? Yes No
Verified answer

Chriddle 8,515 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
or with time:
parseDateTime('1/1/1990 11:31 PM', 'en-us', 'd/M/yyyy h:mm tt')

Was this reply helpful? Yes No
KJH1138 53 on at

Like (0)

Report
Copy link

Link copied!

But why do in one step what I'm able to do in 5? I cannot express how helpful this info is - thank you.

Was this reply helpful? Yes No