Support oData date format in HTTP functions

Dear community,

Some solutions expose APIs with the oData format, often more adapted to the resource models of an ERP or PLM. The Date “CreatedOn”: “/Date(1602547200000)/” format is not recognized as a date in Tulip’s HTTP functions, but as text. When the date is used in a field, it is always possible to transform the text value into a date in the application, but when this date is part of an object or an object table, it is no longer possible to transform the format in the application.

Hi Youri,

Thanks for your request! We’ve improved the parsing of Datetime types in HTTP functions in the r199 release.

Prior to r199, the only date format we parsed into a Datetime type in Tulip was an ISO formatted string.

On and after r199:

  • Values that match the OData format will be parsed as a date with the number value being interpreted as milliseconds since Jan 1, 1970 UTC.
  • Values sent as numbers will be interpreted as the number of milliseconds since Jan 1, 1970 UTC.
  • All other values will be parsed as ISO strings.

Note that this update includes changes to the Connector Host, so on premise Connector hosts will need to be updated after the update is released.

Sound good, thanks for your answer. We will use it as soon our on-Prem connector update is done.