Need More Info
Last Updated: 06 Dec 2019 16:12 by ADMIN
Created on: 11 Apr 2013 21:26
Category: Date/Time Pickers
Type: Feature Request
Support binding of DateTimePicker to type DateTimeOffset
Globalized applications use the DateTimeOffset type instead of DateTime since it includes the offset from UTC for different time zones. If DateTimePicker could bind to this type it would simplify UI development. It would have to have the offset or timezone value provided as either a property or as a second binding.
Maria Veledinova
Posted on: 06 Dec 2019 16:12

Hi everyone,

We understand that this is important functionality and we are actively looking at the suggested option to bind DateTimePicker to a datetimeoffset.

We would appreciate if you share with us use cases where you would use the DateTimePicker  with datetimeoffset. What presentation of the "offset" part would work best for these scenarios?  Also regarding the values posted to the server - would you need to post datetimeoffset or you would need UTC date + offset separately, or you would need both. Sharing such details with us will help us better understand your needs and come up with a  feature that really works for you.

Kind Regards, Maria Veledinova Progress Telerik

Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
Imported User
Posted on: 07 Aug 2018 21:17
Telerik,  Do we have any update on this?
Posted on: 20 Mar 2018 11:14
DateTimeOffset was suggested as way to go back in 2012, please implement datetimeoffset support!
Posted on: 26 Jan 2018 00:11
Microsoft state that DateTimeOffsets should be used instead of DateTimes in almost all situations.  On that basis all of the Telerik controls really should support this out of the box.  It's been years since this was raised as an issue, a fix is long overdue.
Posted on: 13 Nov 2017 13:56
I also think there should be some kind/level of support too - even if it's only a utility function to assist, as otherwise the DatePicker control is useable (- without a manual work-around)..

(It's sad that this is the first time I'm trying to use the control & already it's fallen-over at the start-line.)
Posted on: 03 Oct 2017 10:21

Do you have this planned for any known release?

Posted on: 14 Jul 2017 11:45
What is the delay? Get on with it!
Posted on: 30 May 2017 21:21
I was getting ready to recommend we make a purchase of Kendo.. assuming that the OData support would be OOTB...

I understand why a software shop might hesitate -- since Microsoft has kinda revamped OData versions willy-nilly.. and then only supported the standard in their API libraries, sub-par, themselves, for some time.

However, putting Odata aside, consider that the DateTimeOffset SQL data type has been a while around some time now and was actually Microsoft's recommended date structure for greenfield application development.
Posted on: 14 Jan 2016 18:35
I would like to request that the DateTime Pickers support UTC and DateTimeOffset. The value recieved should be converted to the clients timezone/offset for display purposes and on the backend have a hidden input for the UTC version to post to the server
Telerik Admin
Posted on: 02 Sep 2015 09:10
Thanks for the feedback, folks. We'll have this on our radar for the future releases of the DateTimePicker widget.
Posted on: 01 Sep 2015 22:13
My date-times are all DateTimeOffsets. Can't use Kendo MVC helpers for any time related properties.
The request for this feature is over two years old, still no progress.
Imported User
Posted on: 18 Feb 2015 17:43
I would love this feature. 

Is the limitation how JavaScript handles UTC? If so, then maybe would be useful.
Posted on: 18 Nov 2014 21:55
I totally agree with that. In my opinion not only in DateTimePicker but also in all DateTime related portions of Kendo UI like Grid binding and column filtering, DateTimeOffset type should be supported.
Posted on: 20 May 2014 16:10
Yes! Very much need support DateTimeOffset. At the time of the client's browser contains a component of time offset, which can (and must) to be transmitted to the server when using DateTimeOffset. Thank you! :)