Skip to Content

Timestamp and miliseconds in IoT Service

Feb 05 at 07:13 AM


avatar image


when using the IoT Service on SAP NEO platform, the predefined "date" datatype does not allow for miliseconds. It only allows integer type timestamps.

How could we account for smaller time intervalls ?

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Anton Levin
Feb 05 at 07:40 AM

Hello Marcus,

"date" type [1] in the IoT Service Neo could either a Unix time, represented as seconds since January 1, 1970 or represented as ISO 8601-compatible string. An example with milliseconds is "2016-01-14T08:01:02.123Z"



Show 3 Share
10 |10000 characters needed characters left characters exceeded


thanks. I tried it and post to IoT like


but i see in HANA db only seconds

Sat May 11 2019 12:59:04 GMT+0000 (UTC)

What am I missing ?


I guess this is just a matter of how HANA Cockpit represents the value. MMS Application Data (UI5) does the same, by the way:

If you consume it with MMS OData API, the the value is exactly what you are expecting for:

  <title type="text">T_IOT_M0T0Y0P0E1</title>
  <category term="" scheme=""/>
  <link href="T_IOT_M0T0Y0P0E1(G_DEVICE='d000-e000-v000-i000-c000-e001',G_CREATED=datetime'2018-02-07T14%3A00%3A41.231',C_SENSOR='sensor1',C_VALUE='21',C_TIMESTAMP=datetime'2019-05-11T12%3A59%3A04.999')" rel="edit" title="entity0"/>
  <content type="application/xml">


I consume it with a web service from a view in HANA to display in Analytics Cloud. However neither the data in the db nor the service data show the miliseconds. Also in the service test screen I cannot post the miliseconds. If I e.g. your format proposal, the HANA DB shows:

The message was


unbenannt.png (4.2 kB)