Skip to Content
1
Jan 02, 2019 at 03:47 PM

C4C not recognizing TimeZone on OData Services

264 Views Last edit Jan 08, 2019 at 11:35 PM 2 rev

Hello everybody, first of all happy new year!

I'm currently testing and checking the OData services, that will supposedly come also to ByD, as SOAP will be soon deprecated by SAP.

However there's a major issue that I'm encountering, and it is basically related to the dates behavior.

For instance, I want to save a Ticket with a received date of: 2019-01-01T13:00:00 UTC-5, both the date, and the timezone are two different parameters in the JSON:

{
"ServiceRequestUserLifeCycleStatusCode" : "1",
"Name":"Test",
"DataOriginTypeCode":"7",
"BuyerPartyID":"88885129",
"RequestInitialReceiptdatetimecontent":"2019-01-01T13:00:00",
"RequestInitialReceiptdatetimeZoneCode":"UTC-5",
"ProcessorPartyID":"john.malkovich@sap.com",
"ServiceSupportTeamPartyID":"CO_OE_072"
}

But something is happening and when I check the dates in the system (with an user that has UTC-5 configured as timezone) I can visualize the date as 2019-01-01 (the date that I sent) with date time 08:00:00 (five hours less).

It seems like it is sending the 13:00:00 without timezone, and as far as I know, I'm sending it correctly (since i've done some queries to the system to check the format of the timezone, and it is in fact 'UTC-5')

I can just simply remove 5 hours to the time I send within the JSON, but if somehow it starts recognizing the timezone afterwards, I'll have a heck of a mess.

Does anybody have any insights on this?

Regards,