Timezone bug in Schedule?

Question

Hello, it seems there is a timezone bug in the EJS().Schedule control. Or I am doing something wrong.

My view looks like this:

    @(Html.EJS()
          .Schedule("schedule")
          .EventSettings(es => es.DataSource(dataManger =>
          {
              dataManger.Url("/api/districts/" + Model.DistrictId + "/calendar")
                  .Adaptor("WebApiAdaptor");
          }))
          .Render()
          )

I am in the US Central Timezone, when I create an appointment at 9AM, I see the POST request to my api with the following data:

{
    "Id": 13,
    "Subject": "Fri 9AM",
    "StartTime": "2018-06-09T14:00:00.000Z",
    "EndTime": "2018-06-09T14:30:00.000Z",
    "IsAllDay": false
}

As you can see, the times get converted to UTC (which seems correct), however the appointment itself shows up at 12PM instead which I can't make any sense of.

I have tried all combinations of setting .TimeZone() Start/End TimeZone to not avail.

FYI: I'm doing all this work for a client who purchased a license to this product and asked me to use it against my recommendation. So far, the lack of answers to my inquiries, bugs and lack of updated documentation are making my case towards dropping syncfusion off our project.

Velmurugan S · Answer

Hi Victor,   
  
Thanks for Contacting Syncfusion Support.   
  
We have analyzed the reported scenario and we suspect that the reason for the issue might be some datetime conversion is used within your WebApi controller method while saving the appointment. Therefore, we request to check any conversion used in your application and then check the start and end time value of saved data in database table and the same in the browser network tab response section.   
  
For your reference we have prepared the Schedule CRUD sample by using the Url Adaptor. Since, our WebApiAdaptor can be used to interact with the web Api’s that are created with OData endpoints. Also, it is purely extended from ODataAdaptor and therefore, the endpoint should understand the OData formatted queries. Here, in our Schedule project, the request made through webApi adaptor is not processed with any odata end points– and therefore, we suggest you to use the UrlAdaptor instead of the WebApiAdaptor with which you can create, update and delete any kind of appointments successfully.   
   
http://www.syncfusion.com/downloads/support/forum/138024/ze/ScheduleSampleCRUD1390937300     
   
Kindly check with the above suggestion and sample, if you still facing the same issue at your end revert by sharing some more details like System Time Zone, Controller page code example and appointment object (ex: Start and End Time) values details saved in the database table and then returning appointments data from the controller page to the Scheduler control or reproduce the issue in the above sample. This information will be more helpful for us to analyze your reported scenario further and provide you the possible solution.   
   
Note: We are deeply regret for the delayed response and the inconvenience due to that. Currently, we are drafting complete UG documentation on how to use the scheduler in combination with various other features and will publish it soon in this Volume-2 2018 release for sure. Also, we will update the details for your all your queries and a solution for the bugs if you are reporting related to JS2 Schedule control as much as possible.   
  
Regards,   
Velmurugan