Unanswered

Date and time value of one SharePoint List does not pass to another SharePoint Event List Start Date

(0) Share

Report

Posted on by ChiranJay

Hi Team,

I have SharePoint list that has a form customised using PowerApps. In that form I have a textbox that contains a Date/Time value.

When I pass this value as another SharePoint Event List's Start Date, the date passes correctly but the time has a 17 hour difference.

To pass the value I'm using a PowerAutomate flow that will create a new item in SharePoint Event List.

As an example SharePoint List 01 date and time as 31-03-2022 06:00 PM but SharePoint Event List as 31-03-2022 11:00 AM.

Basically the time is not identifying properly. SharePoint list 01 date and time value is converted from text to DateandTime using the

Text(DateTimeValue(DataCardValue26.Text ), DateTimeFormat.ShortDateTime )

function.

By default SharePoint Event List's Start Date is as DateandTime.

I think this time portion from SharePoint 01 is not passing correctly.

I can't understand the issue with this.

Please help.

Thanks in advance.

Categories:

Using Apps Using Formulas

All responses (2)

Answers (0)

TheRobRush 11,121 Super User 2025 Season 1 on at

Like (0)

Report

Re: Date and time value of one SharePoint List does not pass to another SharePoint Event List Start Date

Here is an example where I had to deal with that

In following as a form has been filled out, it pulls all its data, one of the records we create later is date, and so to get that date in MY time I subtract 7 hrs from flows date which is utc (utc doesn't observe DST, so need to change my flow when time changes)

Now when i input date later i reference my past time instead of time of the submission
TheRobRush 11,121 Super User 2025 Season 1 on at

Like (0)

Report

Re: Date and time value of one SharePoint List does not pass to another SharePoint Event List Start Date

you are probably displaying time in powerapps in your local timezone, and somewhere in transfer process it is getting converted to UTC. Check what time difference is in your area and UTC and if it matches that is the issue. FLOWS pretty much look at dates and times exclusively in utc, at least by default, in my experience