We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy.
Unfortunately, activation email could not send to your email. Please try again.

Schedule Time zones fields

Thread ID:

Created:

Updated:

Platform:

Replies:

130318 May 5,2017 08:21 PM May 8,2017 04:38 AM ASP.NET Core 1
loading
Tags: Schedule
dsapo
Asked On May 5, 2017 08:21 PM

Hi Support:

We noticed that the Schedule table has two time zone columns (StartTimezone and EndTimeZone).

Can we remove one of them to keep just one timezone column that we will apply to the Start and End dates.

In which case should be need to keep two separate fields?

Thanks in advanced

David

Karthigeyan Krishnamurthi [Syncfusion]
Replied On May 8, 2017 04:38 AM

Hi David, 
 
Thank you for contacting Syncfusion support. 
 
StartTimezone and EndTimeZone fields are used to store the timezone values selected for Start Time and End Time fields in appointment window. Previously, to render an appointment as same as the time given in data base, values for the timeZone (sample side), StartTimeZone and EndTimeZone (data base) fields must be maintained same, therefore those twos fields were maintained in the database. In latest release, it is not required to maintain those two fields in database as setting an API applyTimeOffset to False will render an appointment as same as the time given in data base.  
 
 
Regards, 
Karthigeyan 


CONFIRMATION

This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.

;