Method:API Q&A

Re: Time Zone Problem

Method_Victor — Fri, 27 Aug 2010 13:52:04 GMT

Hi Seny,

We've looked into the problem of MethodAPISelect_DataSetV2 returning date in the incorrect timezone, we've applied a fix, and now, the DataSets are always going to be returned in UTC time. If at any point you would prefer to use MethodAPISelect_XMLV2, you will be happy to find out that it also returns dates in UTC time.

Thank you
Victor

Re: Time Zone Problem

seny — Wed, 25 Aug 2010 17:21:53 GMT

When I insert into a date time field using the API, I am passing the UTC time, and in Method itself it displays the right time. However, when I use MethodAPISelect_DataSetV2 to get the time back, there is a 5-hour difference. For example, in Method it displays Aug 25 2010 10:09 AM and in my own application it displays Aug 25 2010 03:09 PM. Our time zone is (UTC-08:00) Pacific Time (US & Canada). Should the difference be 8 hours, instead of 5 hours? Or since it is daylight saving time, should it be 7 hours?

I have not tested the MethodAPISelect_XML yet, but I like using MethodAPISelect_DataSetV2 more than the XML version, as I can just pass the dataset from the MethodAPISelect_DataSetV2 to my GridView, where for the XML version I have to do extra work.

Is that possible to make the MethodAPISelect_DataSetV2 return the UTC time?

Thanks

Re: Time Zone Problem

Anonymous — Tue, 01 Dec 2009 16:36:05 GMT

Matt,

All date/time values are stored in the database as UTC time. When a user logs into Method, the user's local time zone is determined as well as if Daylight Savings Time is currently in affect from the browser on the computer. The offset amount, in minutes, is used on each screen.

This offset amount adjust the UTC time stored in the database to the local time whenever you show the information in a grid or a field on the screen. So the time changes will be shown properly when DST shifts.

Now I went through some example trying to set values in the past through the API. I was using VB.net. If I set the time to July (7/1/1980 00:00:00) and then convert to UTC, the time showed correctly in Method. If I did the same for January (1/1/1980 00:00:00), the UTC time was off by one hour. I checked the database and the UTC time was off by one hour for January. So it appears .NET is performing a DST offset automatically when calculating the UTC time.

So when creating the time in the past, you may have to make the adjustments before sending the information to the API.

If you need to query the information from the database, use the MethodAPISelect_XML and you'll see the UTC record for date/time fields.

If there is anything else I can help you with/clarify please let me know.

Peter

Re: Time Zone Problem

Matt — Mon, 23 Nov 2009 13:25:21 GMT

Peter,

How does Method account for daylight saving when displaying the information back? I have quite a few jobs that were transferred with a start date of Jan 1, 1980 12:00 am. Now in QXO I have a bunch of jobs with the due date start of Dec 31, 1979 11:00 pm. It is possible that those jobs were transferred in the day or 2 before I corrected the problem, but it looked like there was too many.

My concern is that if the is a 5 hour time difference when I transfer the data and then 6 months later the time changes... is the time still going to show correctly?

Re: Time Zone Problem

Anonymous — Wed, 11 Nov 2009 14:27:22 GMT

Matt,

That's the way Method saves information as well. We find the Time Zone from the user's browser and then add 60 if there must be an adjustment based for daylight savings time.

Peter

Re: Time Zone Problem

Matt — Mon, 09 Nov 2009 22:05:15 GMT

Peter,

Here is the code I am using to convert the time:

Dim d As Integer
        Dim mo As Integer
        Dim yr As Integer
        Dim hr As Integer
        Dim min As Integer
        Dim sec As Integer
        Dim mil As Integer

        Dim OldDateTime As Date
        OldDateTime = sInput
        d = OldDateTime.Day
        mo = OldDateTime.Month
        yr = OldDateTime.Year
        hr = OldDateTime.Hour + txtTimeAdjust.Text
        If hr > 23 Then
            hr = hr - 24
        End If
        min = OldDateTime.Minute
        sec = OldDateTime.Second
        mil = OldDateTime.Millisecond
        fnTimeZone = mo & "/" & d & "/" & yr & " " & hr & ":" & min & ":" & sec

the txtTimeAdjust is an integer based on the time zone

                If comboTimeZone.SelectedItem = "Eastern" Then
                    Form2.txtTimeAdjust.Text = "5"
                End If
                If comboTimeZone.SelectedItem = "Central" Then
                    Form2.txtTimeAdjust.Text = "6"
                End If
                If comboTimeZone.SelectedItem = "Mountain" Then
                    Form2.txtTimeAdjust.Text = "7"
                End If
                If comboTimeZone.SelectedItem = "Pacific" Then
                    Form2.txtTimeAdjust.Text = "8"
                End If

I had to add 1 to each of these the day after the time change to have the times be correct. Items that I transferred before the daylight savings switch are all now 1 hour earlier. If there is a better way, please let me know.

Re: Time Zone Problem

Anonymous — Mon, 09 Nov 2009 21:51:12 GMT

Matt,

How are you adjusting for the time zone? Are you converting the date to UTC time or just adjusting the time?

If you can send some sample code of how you are generating the date that would be helpfull.

Peter

Time Zone Problem

Matt — Wed, 04 Nov 2009 14:36:40 GMT

I am using the API Insert/Update to insert the duedatestart(activity table) field. In order to get the time portion to be correct, I need to adjust for the difference in time zones. That worked fine until the time changed this past weekend. Now everything that gets updated is an hour off. Any suggestions on the best way to handle this?