Summary

When JSM Assets data is moved from one environment to another, the import process does not retain the actual Created and Updated attribute values(timestamps) of the object, instead it sets the values when import had taken place.

This Feature Request would address this issue: JSDCLOUD-12388 - Getting issue details... STATUS

Environment

JSM Assets

Cause

As per the current design, the original values of Created and Updated in an Assets object aren't imported.

Solution

While there is no way to import the actual Created and Updated dates, you can try the below alternative to ensure that these dates are still imported for your reference:

1. Open the object schema
2. For each object type, click on the cogwheel on the right of the screen
3. Click Export objects to export the objects. Refer to Export objects
4. The object data will be exported in a CSV file and the file will contain 2 columns - Created and Updated
5. In destination JSM Assets(where you are importing the data), create 2 attributes of type DateTime. Name them: Created on and Updated on
6. In the Import configuration, create an object type mapping between Created - Created on and Updated - Updated on 

Refer: Create attributes and references from your data

Note:

After import, the object keys are usually recycled. So use Name or any other unique attribute when comparing the objects between the exported file and the imported objects.