Hi ,
I am using the scheduler to store recurring appointments for Australia.
One of my recurring appointment is crossing the daylight saving time change date ( 1st April ).
I am storing the exception rules in UTC time as the appointment in used in multiple time zones.
Now, I am facing an issue, wherein, If I create an exception for 26th March the exception rule is updated as 20180327T090000Z ,
which is correct ( 8 PM AEST to UTC ) and If I create an exception for 2nd April the exception rule is updated as 20180402T100000Z
which is also correct ( 8 PM AEDT to UTC )
However, the schedule is still showing the 2nd April Appointment despite being added in the exception, as it can not identify the Daylight savings.
Can you please check this and let me know how this can be resolved.
Hello Peter,
It will take us some time to research this case. I am going to update this thread as soon as possible. Meanwhile, I would like to clarify how you set up a time zone. Have you set the timeZone field directly or do you use the OS settings? Would you please also specify the exact time zone from the list that you are using.
By the way, it will be helpful if you send us the scheduler settings you are using and the data you use to generate an appointment? I hope to hear from you soon.
Hi Maxim,
Thanks.
I am using Australia/Canberra timezone.
Also, I am not setting any timezone, just using OS TZ settings.
Below are the scheduler settings
Also, scheduler seems to behave weirdly.
not correct ( It shows me start time of the previous appointment )
Thank you for your clarification, Peter.
Posting multiple questions within a report makes it difficult to properly track and process such items.
In order to better serve you and track multiple questions in your inquiry, we have taken the liberty of separating the issues you addressed. For quick and efficient responses to your concerns, we kindly request that future inquiries address one issue at a time. Your time and cooperation are appreciated.
Please refer to these reports for further correspondence on these items.
As for your original question, I have passed this thread to our developers for further research. Once we have some updates, we will notify you.
Hi,
Do we have any update regarding the daylight time issue?
We are still working on it. Once we have any news, we will notify you.
Hello Peter,
Right now we are working on the date exception functionality to fully support different time zones.
At the same time, to check if your case can be fixed, we would like to ask you to change the following example
https://codepen.io/ksmo/pen/ELyZxV
This will help us provide a more precise fix for you. I hope to hear from you soon.
Hi Maxim ,
I managed to replicate the issue even in your demo sample for timezone support
please see below plucker
https://plnkr.co/edit/CrN0ipyek3WCN6wQQsBI?p=preview
Step to reproduce :
Go to calendar day view
Open any recurring appointment
delete once occurrence
Expectation: it should be deleted from the view.
Issue:
Instead of deleting it, scheduler appends it to the beginning of the day ( 0800 am ) despite of having the recurrence rule.
I did it the demo code for devextreme timezone demo as well.
I am using the exact structure in my code.
Peter,
The provided description is not quite clear to me. Would you please clarify how it relates to the original issue, exception dates and time shaving in AEDT time zone? Did you face another issue? Please clarify this. Would you please also record a screencast to illustrate the steps in action? I believe it will make the case clearer.
We reviewed your description again and now the case is clear. Our developers are working on it.