Avoid using Timezones and dst in the Schedule

[dsapo]

Hi Support:

We are facing several issues with the timezone handling, because we used the datetimes from the Schedule table in different parts of the web site.

Would be possible to avoid completely using timezone and dst in the Schedule control, so when you create an appointment for example as 2:00 PM, is stored in the database as 2:00 PM without any UTC conversion.

If thats not possible, what would be the correct approach to work with UTC and DST when you have user around the world.  Should every user will have to define their UTC and DST in our system, because using the Schedule control ?

Appreciate any guidance or best practices about this topic.

Thanks

David

[Karthigeyan Krishnamurthi]

Hi David, 

 

Thank you for contacting Syncfusion support. 

 

To render an appointment as same as the time given in data base, we suggest you to set apply-time-offset to false and for the same we have prepared the sample which can be download from the below location. Kindly view the below code example used in the sample. 

http://www.syncfusion.com/downloads/support/forum/129809/ze/Sample-283748486 

 

<Code> 

<ej-schedule id="Schedule1" width="100%" height="525px" create="onCreate" current-date="new DateTime(2014, 12, 5)"> 

    <e-appointment-settings apply-time-offset="false" id="Id" subject='"Subject"' start-time='"StartTime"' end-time='"EndTime"' all-day='"AllDay"' recurrence='"Recurrence"' recurrence-rule='"RecurrenceRule"'> 

        <e-datamanager url="Home/GetData" crud-url="Home/Batch" adaptor="UrlAdaptor"></e-datamanager> 

    </e-appointment-settings> 

</ej-schedule> 

</Code> 

 

 

Regards, 

Karthigeyan 

[dsapo]

Hi Karthigeyan:

Our situation is that we need to store the  database datetimes equals to the datetimes selected in the appointment view.  Currently the database is showing the datetime with an timezone offset.  In the Schedule is fine, but we need to keep the same datetime in the database.

Any idea.

Thanks again

David

[Karthigeyan Krishnamurthi]

Hi David,  

  

Thanks for your update. 

 

By default, in Asp.Net Core sample, appointments are saving at 0 UTC when the CRUD operation is performed. For example, if an appointment is saved at 2-3 PM (with system timezone as UTC +5.30) in Scheduler, appointment will be retrieved as 8.30-9.30 AM (with UTC 0) at controller function before saving it in data-base. System timezone is then added with an appointment duration (converted to 2-3 PM) and sent to the Scheduler source from controller. In Scheduler default addition of system timeznoe is prevented by setting apply-time-offset to false, therefore finally appointment is rendered at 2-3 PM in Scheduler. Due to these behaviors, it is not possible to achieve your requirement. 

 

Regards, 

Karthigeyan 

  

[dsapo]

Thanks Karthigeyan  for the explanation.

[Sellakumar]

Hi David, 

 

We are glad to hear this from you. Kindly let us know, if you need any further assistance on this.