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.