Issue Summary

When conducting an assets import, integers representing a datetime in Unix Epoch time format with second, millisecond or microsecond precision do not parse, resulting in an empty datetime on the assets object.

Steps to Reproduce

• Create a new empty assets object schema and assets object type, which includes a new attribute of type 'DateTime' 

• Construct a csv with the following content

name,integer_datetime_representation
"Test Object",638292024000000 

(Representing a date in year 1990 when parsed in Unix Epoch format, with microsecond precision)

• Create a new csv import configuration for the new assets object schema, uploading the above csv file (all other configuration can remain unchanged).

• Create an object type mapping to the new csv import (all configuration in the create modal can remain default), set data locators and matching assets attributes after creation.

• Run a sync.

• Review the newly imported assets object.

Actual Results

Created assets object does not have a datetime set.

Expected Results

The datetime is correctly parsed and set on the new assets object.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available

Versions Tested

Please confirm all versions that have been tested for this issue, and indicate whether the tested version is affected or not affected, below: