Skip to Content

Recently I was struggled with a customer incident and finally I realized that I didn’t understand the Edm.DateTime quite clearly. So I spend some time to do research on it to fix my knowledge gap. I list my learning here in case any other guy needs it as well.

For my study, I use this field in my application for example.


It is bound to json model field “ClosingDate” with a formatter.


In the metadata, this field is defined with type Edm.DateTime (Represents date and time with values ranging from 12:00:00 midnight, January 1, 1753 A.D. through 11:59:59 P.M, December 9999 A.D.)


After I change the closingDate to 2015-10-3 and save the change:


The saved opportunity is reread from backend with an odata request. In Chrome network tab I observed the closingDate has this format: /Date(1443830400000)/:


What makes me curious is when I directly paste the url of the odata request to Chrome or SAP gateway client, I get the closingDate with this format instead. The figure below is response in Chrome:


And this is response from gateway client.


Why is there difference between them?

And when I type “alert(new Date(1443830400000));” in chrome console, I get this popup:


Actually it ( 2015-10-03 08:00:00 GMT +0800 ) points to exactly the same time as 2015-10-03 00:00:00 UTC.

So how could the date with format /Date(1443830400000)/ be consumed in my application?

It makes sense to start debugging via the framework handler when the response of odata request ( Opportunity re-read after closing date is changed ) is successfully returned:


check the body field:


The aim is to figure out how framework parses this /Date(1443744000000)/.

Then I reached the place:

  • there is a regular expression which extracts the number 1443744000000 from the input string.
  • a local time is returned by new Date(), with the number parsed by previous step passed in. The local time is returned based on current Time zone configured in my laptop.


Thanks to the framework, which has parsed the raw json response string to Javascript object, so that we application could directly use the converted object to bind our model.


Then the local time returned by framework will be passed into my formatter so now I could do any formatting based on customer requirement:


To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. José Antonio Ruz Polanco

    This is a very interesting topic, even when I know is old, I will like to ask, If we need to send some date back in the URL of an OData Model read command, for a query, we would need to convert back that date to milliseconds?


  2. Neelima Nebhani

    Hi Jerry,

    Thank you for above information. It helped clearing my concepts.

    But I am facing an issue with the above method.

    Users from Chile(Timezone: UTC-6) are facing issue as they are getting one day previous date as compared to ECC dates.

    Can you please suggest what might have gone wrong?


Leave a Reply