Strategy recommends that you observe the following practices when copying objects with Object Manager in Strategy 10.x:
- Back up metadata before copying any objects. Object Manager cannot undo the copying and replacing of objects.
- Ensure that the Dependency Search, Conflict Resolution, International, and Migration options in the Object Manager Preferences dialog box are set to fit your project’s needs.
- Copy application objects into the following project folders:
- My Personal Objects or any subfolder of My Personal Objects
- Public Objects or any subfolder of Public Objects.
- Copy schema objects into the appropriate Schema Objects sub- or descendent folders only. For example, if copying a hierarchy, only paste the hierarchy into the Project Name\Schema Objects\Hierarchies folder.
- When copying MDX cubes between projects, make sure that the conflict resolution action for the cubes, cube attributes, and reports that use the cubes is set to Replace. Refer to Technical Document below for recommendations for migrate MDX cubes:KB20124: Best practices to migrate cubes (SAP BW, MSAS or Essbase) and cube objects (attributes) using MicroStrategy Object Manager
- If there is a need to copy objects from multiple folders at once, create a new folder, and create shortcuts in the folder to all the objects you want to copy. Then copy that folder. Object Manager copies the folder, its contents (the shortcuts), and their dependencies (the target objects of those shortcuts) to the new project.
- Another way to copy objects from multiple folders at once is to create an update package from the source project, and then import it into the target project. For more information about update packages, including step-by-step instructions, refer to Technical Document below:KB31821: How to create an Object Manager Package for transfer of objects between metadatas in MicroStrategy 9.4.x-10.x?
- If using update packages to update the objects in your projects, use the Export option to create a list of all the objects in each update package.
- When copying objects that contain location-specific strings (such as metric aliases, custom group names, or text boxes in documents), make sure to either disable Advanced Conflict Resolution, or use the same option in the translation preferences and in the conflict resolution. Otherwise there may be inconsistencies between the object definition and the translation in the destination project.
- Regardless of the translation preferences, when copying objects with location-specific strings always verify the results. For example, empty translations in the source or destination may result in incorrect transactions being saved with the new object. Use Integrity Manager to identify reports or documents that have unexpected translations.
For more information about Object Manager, refer to the following knowledge base document:
KB4609: MicroStrategy Object Manager Frequently Asked Questions (FAQ)
Article Reference Number: KB441660
