[DevExpress Support Team: CLONED FROM T632271: The Scheduler does not save recurrence exceptions in the start date time zone with the hotfix of the T619455 ticket]
I need the opposite behavior where the exception time is stored using the timeZone of the scheduler and not the local browsers time zone. How can that now be accomplished? As of 18.1.7, the recurrenceException is using the right day but local time zone.
Scheduler - The recurrence exception rule doesn't take the timeZone option value into account
Answers approved by DevExpress Support
created 6 years ago
(modified 6 years ago)
We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.
Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.
Show previous comments
(6)
Hi Greg,
This logic is working fine on my side (see the attached screencast). Would you please specify your current time zone in OS?
Hi Greg,
Thank you for the clarification. As the issue is specific to particular time zones, I created a new report on your behalf:
Scheduler - The recurrence exception rule has incorrect value if the Central Time (UTC -06.00) time zone is used
We'll update it once we have any news.
Hi Greg,
The recurrence exception used by Scheduler and automatically processed according to the specified timeZone option value. Would you please clarify why you need to store this value according to the timeZone option value? Would you please modify my example to illustrate when the default implementation doesn't work.
The timezone for the scheduler is specified as Etc/UTC so your statement of 'automatically processed according to the specified timeZone option value' should mean that the recurrence exception should be stored in the same time zone correct? If your answer is yes, then this is the issue because it's not.
For example, in the CodePen same (either yours or mine), there are recurring appointments on 10/3 through 10/7 at 6:00 AM - This time is in Etc/UTC because I have specified the timezone. If I drag the appointment for 10/4 to an hour earlier on the week view, if you look at the console log, you will see that the recurrenceException field contains 20181004T010000 for the series appointment. The time in the recurrence exception got pushed back another 5 hours because of my local browsers timezone. This doesn't seem right since I am specifying Etc/Utc as the timezone to use. The exception should be 20181004T050000.
https://codepen.io/gknierim/pen/RqNvpQ?editors=1010
Please let me know what I am missing here.
Thanks,
Greg
Thank you for the clarification. We need additional time to research if we can support this scenario at the widget level. Please bear with us.
We didn't completely fix the issue in version 18.1. We will update this ticket when we have any results. We appreciate your understanding.