Recurring event with timezone shown incorrect after remove an exception

[Max]

I try to use the scheduler with timezone.

For example, I ajdusted "Africa/Nairobi" (GMT+03:00 Nairobi) timezone for the scheduler.
I'm creating a daily recurring event with timezone "America/Sao_Paulo" (GMT-03:00 Brasilia) at 1:00 PM. And create an exception for this series, just changing description.
The series and exception shown correctly on the scheduler at 7:00 PM.
After I removed the exception, the series moved and shown at 1:00 PM on the scheduler.

I tried to use setting "timezone" of datasource to set "Africa/Nairobi" and tried adjust currentTimeMarker property but it is not help.

I can to reproduce it on the http://dojo.telerik.com. Just open http://demos.telerik.com/kendo-ui/scheduler/index and click on "Edit This Example" and just change timezone to "Africa/Nairobi" in the code.

[Georgi Krustev]

Hello Max,

The scheduler timezone option represents the server location (its timezone). Nevertheless the described issue is observable on our end using "Etc/UTC" timezone too. We will further investigate the case and will let you know what our findings are soon.

Regards,
Georgi Krustev
Telerik

 

 

[Max]

Thanks for reply

[Georgi Krustev]

Hello Max,

We further reviewed the case and can clarify that the series re-position is expected when the recurrence head is updated due the removed exception event. To describe the scenario better let's review the taken steps:

• A recurrence head that starts at 10:00 AM with "America/Sao_Paulo" (GMT-03:00 Brasilia) timezone, will be displayed as 1:00 PM in Scheduler with "Etc/UTC" timezone (I am using UTC timezone for easier calculations)
• Once the exception is removed, we convert the start/end values from "Etc/UTC" to "America/Sao_Paulo" (from 1:00PM to 10:00AM) to perform the recurrenceException field update. This conversion is required. It is visible because any source update is displayed directly in the views
• Once the event is updated (after CRUD operations), the recurrence series is re-adjusted back to the old position

The described steps can be observed in this screencast:

• http://screencast.com/t/aE2PutvrU5pV

That being said, the only reason for the described erroneous behavior is incorrect setup of the server part - the dates are not send/received in UTC (this is obligatory). If the widget's timezone is not set correctly - it should reflect the timezone of the server.

Regards,
Georgi Krustev
Telerik