AnsweredAssumed Answered

Datetime field issue in leadchanges.json

Question asked by 97df00c9deaa594351715b121ebc2d5286476985 on Aug 3, 2017
Latest reply on Aug 4, 2017 by 97df00c9deaa594351715b121ebc2d5286476985

I am using REST API to get the list of updated lead activities. Few of the fields I'm monitoring are 'datetime' format and they seem to return a wrong time.

 

Here are more info:

 

Request URL: /rest/v1/activities/leadchanges.json

 

Result Response:

{

  "requestId": "d94a#15daa2224bf",

  "result": [

    {

      "id": 111

      "marketoGUID": "111",

      "leadId": 111,

      "activityDate": "2017-08-03T22:05:21Z",

      "activityTypeId": 13,

      "fields": [

        {

          "id": 111,

          "name": "dateTimeField",

          "newValue": "2017-08-10 16:00:00", // set to 2 PM

          "oldValue": "2017-08-10 15:00:00"   // set to 1 PM

        }

      ],

      "attributes": [...]

      ]

    }

  ],

  "success": true,

  "nextPageToken": "====",

  "moreResult": false

}

 

When I set the field value to 2 PM, 16:00:00 is returned. The REST response is consistently 2 hours offset. Have anyone come across this and found out the reason why?

Outcomes