Unanswered

Time Issues

(1) Share

Report

Posted on by skoofy5

482

I've got a problem with a time field in a JS resource. I'm expecting the field to return 2/Jan/2022 and it does that for the formatted date, however I can't use the formatted date, I need to use the UTC and offset, but the UTC is being returned as 2022-01-01T13:00:00Z and the offset is 600 which return 1/Jan/2022 23:00:00.

So it's a day out - am I missing something when it comes to conversion?

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (4)

Answers (0)

skoofy5 482 on at

Like (1)

Report
Copy link

Link copied!

Here's some logging out to highlight the issue.

The last three values are the formatted date, the utc and the offset.

Was this reply helpful? Yes No
Diana Birkelbach 3,072 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Hi @skoofy5 ,

It could be a DaylightSavingTime issue. In January we have winter time, so it's an extra hour to consider.

And for that, you need to know the DaylightSavingTime start and end for the country where your user lives.

These issues are so terrible. I feel with you.

Was this reply helpful? Yes No
skoofy5 482 on at

Like (0)

Report
Copy link

Link copied!

Yeah we've thought it might be DST. Though to make it confusing there's another date, saved by the same timezone settings for January that does come out as the 2/Jan...

It's super frustrating.

Was this reply helpful? Yes No
Diana Birkelbach 3,072 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @skoofy5 ,

Maybe the other date on 2.nd January has another time, which doesn't get affected by substracting/adding one hour.

Was this reply helpful? Yes No