EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB439322:Reports migrated by objects package via Command Manager is displayed as <DELETED REPORT> in MicroStrategy Enterprise Manager report


Min Zheng

Senior Manager, Cloud Support • MicroStrategy


SYMPTOM
Reports migrated by objects package via Command Manager is displayed as <DELETED REPORT> in Strategy Enterprise Manager report.
Below is a possible scenario for end users who meet such problem.

  • Data load is scheduled every day.
  • A package has been generated to migrate several objects created in Development Environment to Production environment.
  • The package is imported via Command manager, instead of Object Manager.


 
Below command is used as this package is merged to Production environment via Command manager.


IMPORT PACKAGE "C:\Package1.mmp" [FOR PROJECT "xxxx"]; 

After the migration and scheduled data load, the objects migrated are not updated to the related Enterprise Manager tables.
Even if the data load is manually triggered, the result is the same.
 
CAUSE
Above phenomenon is possible per current function limitation for migrating package via Command Manager.
 
In Object Manager – Tools – Object Manager preference – Migration, below option is available.
Preserve object modification timestamp during migration
Checking this option can retain the object modification timestamp in the destination project, even if the source object has a newer modification timestamp. If this check box is cleared, when an object is migrated into a new project its modification timestamp is updated to the date and time of the migration.

ka04W000001IwHLQA0_0EM44000000QCtq.png

But for Command manager, running IMPORT PACKAGE command would always follow the behavior when above setting is checked. Namely the modification timestamp would never be updated no matter how the option has been set on Object Manager side.
So in above scenario, the objects migrated to Production would preserve the modification timestamp as originally, instead of being updated to the migration date.
Thus its modification time falls out of the next scheduled data load's time window.
Then these objects would never be loaded.
 
This is a special user case caused by limitation on Command manager script until Version 11.0.
 
ACTION
Starting from version 11.0, a new parameter UPDATEOBJECTMODIFICATIONTIME has been supported.
In order not to preserve the timestamp, use below command:


IMPORT PACKAGE "C:\Package1.mmp" [FOR PROJECT "xxxx"] UPDATEOBJECTMODIFICATIONTIME;

This has been documented in KB441552 and Command Manager Guide .
Please add UPDATEOBJECTMODIFICATIONTIME to avoid this issue when migrating package using Command Manager for version above 11.0, e.g version 2020 or version 2021.


Comment

0 comments

Details

Knowledge Article

Published:

December 27, 2017

Last Updated:

August 16, 2022