KB441552: Object manager always doesn’t preserve the object modification timestamp while Command manager always preservers it when importing package in MicroStrategy 10.x

SYMPTOM
Object manager and Command Manager can be used to import package from one environment to another.
However they have different behaviors regarding whether to preserve the object modification timestamp or not.
 
For Object Manager, there is an option “Preserve object modification timestamp during migration” under Object Manager preference-Migration.
However, no matter this option is checked or not, Object Manager will always not preserve the timestamp. The modification time for imported objects will be the time the import is implemented.
 
For Command Manager, below command can be used.

IMPORT PACKAGE "<file_name>" [FOR PROJECT "<project_name>"];

 As no option can be added in command to alter the behavior, Command Manger will always preserve the timestamp. The modification time for imported objects will be the time the object is last modified in original environment.
 
CAUSE
This is a known issue in Strategy 10.x.
 
ACTION
For Object Manager, it is currently under Strategy’s investigation.
 
For Command Manager, it is addressed in 11.0 or above release.
A new parameter UPDATEOBJECTMODIFICATIONTIME has been supported.
In order not to preserve the timestamp, use below command:

IMPORT PACKAGE "<file_name>" [FOR PROJECT "<project_name>"] UPDATEOBJECTMODIFICATIONTIME;

Without the new parameter, it will behave same as in old version. 
The Strategy Internal Reference Number for the issue discussed in this technical note is DE103714 for Object manager and DE67944 for Command manager.
  KB441552