Timezones

A timezone refers to any of the 24 regions loosely divided by longitude and which keep the same time standard.

Getting Started

To set a timezone to the Scheduler, set the timezone option. timezone indicates the desired timezone to be applied when the Scheduler displays the appointment dates. By default, the timezone option is not set and, as a result, the event dates will be created based on the current client timezone offset. This means that users from different timezones will see different start and end times. On the other hand, setting the Scheduler timezone will display the same start and end times regardless of the timezone of the user.

• When you use remote binding, the Scheduler expects to receive UTC dates. Respectively, it will send them back to the server in UTC. The service in use is responsible for keeping the dates in UTC, without offsetting them against its local time.
• When you bind the Scheduler to a remote service, keep the timezone option always set to, for example, "Etc/UTC".
• When the timezone option of the Scheduler is not set, the current system timezone offset is used.
• The recommended Date format for sending and receiving Scheduler event dates is ISO 8601 with a Z zone designator (UTC date). The same format is used by the JSON.stringify method, which converts JavaScript Date objects to JSON strings. The kendo.timezones.min.js file must be included in order to use timezones other than "Etc/UTC".

The following example demonstrates how to set "Etc/UTC" timezone to the Scheduler.

    @(Html.Kendo().Scheduler<Kendo.Mvc.Examples.Models.Scheduler.MeetingViewModel>()
        .Name("scheduler")
        .Date(new DateTime(2013, 6, 13))
        .StartTime(new DateTime(2013, 6, 13, 7, 00, 00))
        .Height(600)
        .Views(views =>
        {
            views.DayView();
            views.WeekView(weekView => weekView.Selected(true));
        })
        .Timezone("Etc/UTC")
        .DataSource(d => d
                .Model(m =>
                {
                    m.Id(f => f.MeetingID);
                    m.Field(f => f.Title).DefaultValue("No title");
                    m.RecurrenceId(f => f.RecurrenceID);
                })
            .Read("Meetings_Read", "Scheduler")
            .Create("Meetings_Create", "Scheduler")
            .Destroy("Meetings_Destroy", "Scheduler")
            .Update("Meetings_Update", "Scheduler")
        )
    )

Reading Events from Data Source

If the timezone option is defined, the Scheduler will remove the local timezone offset, converting dates to UTC. Then, it will apply the defined timezone value, for exampe, America/New_York.

Sending Events to Remote Service

If the timezone option is defined, the Scheduler will remove the applied timezone offset, for example, America/New_York, converting dates to UTC. Then, it will apply the local time.

The SchedulerEvent instances are serialized by using JSON.stringify. In the process, the dates are converted to UTC and then formatted according to the ISO8601 format.

Setting the No Timezone Option

If you do not define a timezone option, your system timezone settings will apply by default.

Live Sample

You can find a full working sample with Timezone defined and different cultures set dynamically here:

Localization and Globalization

See Also

• Server-Side API