Method Community

I wasn't sure where to post this but I think this must be a data issue. We've created an event system using Method and have a table dedicated to creating timelines for events that are driven by a date/time field. We are having an odd problem where reports and the API return the correct value for some records and others return a time 1 hour later than what is in the database. The table NOVAEventMilesotnes is linked to the NOVAEvents table and these errors seem to be consistent across an event. I see no difference in the data when viewed through the UI.

Hi Nick,

You called our support line and we created a case for this. For anyone who may be looking at this post, it appears the API may not be correcting for daylight savings time. We are looking into this and I will update this thread once I have more information.

-Audisho

As I discussed over the phone with Nick, the reason that this occurs is that the API relays all time in UTC and any time zone calculations need to be done by the application that is using the API.

Dev - Can you please comment on this post and possibly point Nick in the right direction with regards to dynamically having his website correct for DST. At this time he has to alter his code when DST starts and ends to correct for this.

-Audisho

Nick,

I'm not sure what language you are using to make the API calls, but there should be a convert to UTC method that you can call on the date before sending it to Method. Here is an example for .net http://msdn.microsoft.com/en-us/library/system.datetime.touniversaltime%28v=vs.110%29.aspx