Sorry for confusion...

[Deadline] [datetimeoffset](7) NULL

should be

[MyDate] [datetimeoffset](7) NULL

I know this is an old post but this worked for me.

// *** TSql ***

CREATE TABLE [dbo].[MyTable](
[Id] [int] IDENTITY(1,1) NOT NULL
, [Deadline] [datetimeoffset](7) NULL
 CONSTRAINT [PK_Task] PRIMARY KEY CLUSTERED 
(
[Id] ASC
) WITH (STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY]

GO

CREATE PROCEDURE [dbo].[UpdateDate] (@Id INT, @DateParam NVARCHAR(50))

BEGIN

    SET NOCOUNT ON;

    BEGIN TRY

        BEGIN TRANSACTION;

            DECLARE @DateOffset DATETIMEOFFSET = CAST(@DateParam AS DATETIMEOFFSET(7))

            UPDATE [dbo].[MyTable] SET [MyDate] = @DateOffset WHERE [Id] = @Id

        COMMIT TRANSACTION;

    END TRY

    BEGIN CATCH

        IF @@TRANCOUNT > 0 ROLLBACK TRANSACTION;

    END CATCH

END

// *** js ***

$("#datetimepicker").kendoDateTimePicker({
    value: new Date()
    , change: function(e) {

        $.ajax({
            url: "/api/UpdateDate"
            , type: "POST"
            , data: JSON.stringify({
                "Id": << record id here >>
                , "Deadline": toDateTimeOffset(kendo.parseDate(this.value()))
            })
            , success: function(result) {
                alert("Update Successful");
            }
            , error: function(result) {
                alert(result.error);
            }
        });
    }
});

/**
 * converts a datetime to a datetimeoffset format for ms sql insert
 * @param {date} dateTime
 */
function toDateTimeOffset(dateTime) {
    var dateStr = kendo.toString(kendo.parseDate(dateTime), "MM/dd/yyyy hh:mm:ss");
    var tzOffset = (dateTime).getTimezoneOffset();
    var tzOffsetHour = tzOffset/60;
    var tzOffsetMins = tzOffset % 60;
    var tzOffsetStr = (tzOffsetHour >= 0 ? "+" : "-") + zeroPadNumber(tzOffsetHour, 2) + ":" + zeroPadNumber(tzOffsetMins, 2);
    return (dateStr + " " + tzOffsetStr);
}

/**
 * zero pad a number as a string to a minimum length
 * @param {number} num
 * @param {number} len
 */
function zeroPadNumber(num, len) {
    var s = "" + num;
    if (s.length >= len)
        return s;
    s = "000000000" + s;
    return s.substr(s.length - len);
}

Telerik,  Do we have any update on this?

DateTimeOffset was suggested as way to go back in 2012, please implement datetimeoffset support! 
https://blogs.msdn.microsoft.com/davidrickard/2012/04/06/datetime-and-datetimeoffset-in-net-good-practices-and-common-pitfalls/

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.

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.)

Hi,

Do you have this planned for any known release?

Thanks,
Gavin

What is the delay? Get on with it!

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.

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

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.

I would love this feature. 

Is the limitation how JavaScript handles UTC? If so, then maybe http://momentjs.com/timezone/ would be useful.

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.

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! :)