cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
afernando
Level 10

Save local time

Hello,

 

I'm trying to save local time to a datatimeoffset column in a SQL server. But powerapps converts local time to +00:00 time zone before saving.

 

Does anyone know how to overcome this issue? 

 

I'm planning to generate a text string in the format of local time eg: "2017-04-06 18:30:00.0000000 +11:00" and write it to the database. But I need to retrieve the local timezone for that. 

 

Any idea how can I achieve this? 

Thanks in advance.

1 ACCEPTED SOLUTION

Accepted Solutions
Meneghino
Level 10

Re: Save local time

Hi @afernando

 

Does this work?

 

Round(24*(Now()-DateTimeValue(Left(Text(Now(),DateTimeFormat.UTC), 16))), 0)
6 REPLIES 6
Meneghino
Level 10

Re: Save local time

Hi @afernando

 

Does this work?

 

Round(24*(Now()-DateTimeValue(Left(Text(Now(),DateTimeFormat.UTC), 16))), 0)
afernando
Level 10

Re: Save local time

@Meneghino

works like a charm. Legend!

afernando
Level 10

Re: Save local time

Hi,

 

While I was able to generate a string that looks like the UTC local time, I'm not having any luck writing the string to the SQL database.

My string looks like this;

 

2017-04-07 13:50:00.0000000 +10:00

 

I can paste this value to the field when connected to the database from MS Acess but PowerApps won't write the value to the field. 

 

Any suggestions?

 

Thanks in advance.

Meneghino
Level 10

Re: Save local time

Hi @afernando

With the current state of PowerApps I would suggest to saving UTC times in a datetimeoffset type of column.

I would not recommend saving local time.

Alternatively, you could save to an integer column yyyymmddhhmmss.  This will allow you to filter and sort properly in PowerApps (currently not possible with datetime columns, I have other posts on this)

Then, when the PowerApps team sort out the problems with datetime columns we can finally migrate back to proper datetime columns.

afernando
Level 10

Re: Save local time

@Meneghino,

 

Thanks for your comment. The problem with saving UTC time is that PowerBI won't let me convert them to local time when connected via DirectQuery. 

The main purpose of my app is to record our production and show the output on a live dashboard. Since DirectQuery doesn't allow converting data types, saving time an integer also not a solution. 

 

I guess I'll have to look somewhere else. 

 

Thanks again.

Anton

Meneghino
Level 10

Re: Save local time

Understood.

I would create a calculated column in your data source that turns UTC to local time.  Then you can direct query that column instead without any loss of performance.  You can even index the calculated column.

This way you can keep the best practice of saving UTC.

Helpful resources

Announcements
firstImage

Watch Sessions On Demand!

Continue your learning in our online communities.

SecondImage

PowerApps Monthly Community Call

Next Wednesday, August 21st at 8am PDT

Top Community Contributors for July 2019

Top Community Contributors for July 2019

Let's thank our top community contributors

Power Platform 2019 release wave 2 plan

Power Platform 2019 release wave 2 plan

Features releasing from October 2019 through March 2020

FirstImage

Power Platform World Tour

Coming to a city near you

thirdimage

PowerApps Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

FourthImage

Join PowerApps User Group!!

Connect, share, and learn with your peers year-round

FifthImage

Dynamics 365 and Power Platform April 2019 Release notes

Features releasing from April 2019 through September 2019!

SixthImage

Power Summit Australia 2019

August 20-23rd 2019

Users Online
Currently online: 207 members 3,692 guests
Please welcome our newest community members: