Skip to Content

Timestamp and miliseconds in IoT Service

Hi,

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 ?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • 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"

    Regards,

    Anton

    Add comment
    10|10000 characters needed characters exceeded

    • 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

      {"mode":"sync","messageType":"m0t0y0p0e1","messages":[{"sensor":"sensor1","value":"20","timestamp":"2019-05-11T12:59:04.999Z"}]}

      unbenannt.png (4.2 kB)