KB219556: Attributes and tables are no longer linked together after being migrated in separate update packages in MicroStrategy Object Manager 9.4.1.

SUMMARY:
This issue is found in Strategy Object Manager 9.4.1.  It affects tables and attributes that are migrated to the same destination, but not in the same package. There’s a chance that they will no longer be mapped together once they’re in the same environment again. This behavior is to be expected when the user does not use "Add All Used Dependencies" during package creation, but an enhancement was logged to alter behavior since using that option is not always feasible for customers with very large environments and schema.
 
SYMPTOM:
A user migrates two linked objects in an environment; One is an attribute and the other is a partition mapping table. The objects are migrated separately, one at a time. In the destination environment, both objects are imported successfully. However, the objects are not linked in the destination environment.
 
STEPS TO REPRODUCE:

1. Create an object manager package with a partition mapping table.
2. Apply the package to the destination environment.
3. Create another package with a linked attribute.
4. Apply the second package to the destination environment.
5. View the objects. They are no longer linked, even though they were linked in the source environment.

 
CAUSE
This is expected behavior in Strategy Object Manager 9.4.1. Ideally, they should link together because their version IDs would match. However, if an attribute and a table are migrated separately, there is no guarantee that they’ll link together once they’re in the same environment again unless the "Add All Used Dependencies" option is checked.
 
ACTION:
If possible, use the “Add All Used Dependencies” option when performing a migration like this. If this is not feasible, contact Strategy Technical Support for an update on this issue.
 

 
WORKAROUND:
Try to migrate the objects in the same package to ensure that they will still be linked in the destination environment. If this is not possible, migrate them separately with the “Force Replace” option selected so that if there’s an identical object in the destination environment, the new table or attribute will overwrite it and hopefully reestablish the table-attribute link.
 

 
VIDEO:
 
 
ADDITIONAL TROUBLESHOOTING:
If the above steps do not work, consider contacting Strategy Support and please have the following information available:
 
The exact types of objects being migrated. Packages containing both objects. A screenshot  of the Object Manager preferences and the Package Creation options to ensure the correct selections were used. A copy of the metadata.
 
TO LEARN MORE:
There are several other Object Manager issues related to the types of objects present in the package. Please review the 'Related Links' section below for additional technotes that include information on related issues.
 
 The Strategy Internal Reference Numbers for the issue discussed in this technical note is 990508.