MicroStrategy Object Manager
MicroStrategy Object Manager is a consolidated interface to manage users and their object libraries across MicroStrategy Business Intelligence applications.
Object Manager makes it easy to migrate specific objects or entire projects from a development environment to separate test and production systems providing full life cycle project management for business intelligence systems. It ensures the consistency of business metadata across development, test, and production systems and provides object impact analysis.
Object Manager includes the following tools:
- Project Merge Wizard: Project Merge Wizard migrates all objects from a source project into a destination project using the specified object migration rules. Project merges are used to synchronize all objects in a project, such as synchronizing a testing environment with a production environment.
- User Merge Wizard: The User Merge Wizard combines users and their related objects from one project source. These objects include profile folders, group memberships, user privileges, security roles, and security filters, among others. Information from the user or group that is being merged is copied to the destination user or group. Then the user or group that is being merged is removed from the metadata, and only the destination user or group remains.
- Packages: Object Manager can create standalone package files containing MicroStrategy metadata objects and use the package files to import these objects to other MicroStrategy projects. These package files can be used to migrate object definitions without a live connection to a source project.
Repository Translation Wizard: The Repository Translation Wizard is a utility that helps you manage object translations for a MicroStrategy project. You use the Repository Translation Wizard to extract strings from MicroStrategy metadata objects and copy the strings into a translation repository. Once the data is in the translation repository, you can use a third-party translation tool to translate the strings into the required languages or you can manually translate the strings. You can then use the Repository Translation Wizard again to import the translated strings back into the metadata and update the object properties with your translations.
The Repository Translation Wizard is especially useful for translating many objects in a metadata at one time. Alternatively, you can translate individual objects, one at a time, using MicroStrategy Developer's functionality.
See the System Administration Help for steps to use MicroStrategy Object Manager to manage objects as they progress through your project's life cycle. Online help is also available for Object Manager. You can access the online help by pressing F1 while using Object Manager.
Compatibility and Interoperability
A project source is required to run MicroStrategy Object Manager and connect to a metadata repository. MicroStrategy Developer and MicroStrategy Object Manager can be installed on the same machine, or on different machines.
For the complete MicroStrategy platform compatibility and interoperability specification, see Compatibility and Interoperability.
For all certified systems, see Platform Certifications.
|Operating System||Processor||RAM||Disk Space|
|Windows||64-bit||4 GB (minimum)||0.5 GB|
Installing MicroStrategy Object Manager
For steps to install MicroStrategy Object Manager, see the Installing MicroStrategy on Windows chapter of the Installation and Configuration Help.
Download the software from the MicroStrategy download site.
If you encounter problems during the installation procedure, please see Troubleshooting in the Troubleshooting appendix of the Installation and Configuration Help. If you require assistance, contact Technical Support.
For steps to install MicroStrategy Object Manager, see the Installation and Configuration Help.
The following table lists folders and files of interest that are included in the default directory structure after an installation of Object Manager.
The default folder is:
C:\Program Files (x86)\MicroStrategy\Product Name when installed on a 64-bit Windows environment.
If installing over previous versions of the product, the folder remains the same.
||MicroStrategy Object Manager root directory|
||Required MicroStrategy Developer files for MicroStrategy Object Manager|
Upgrading MicroStrategy Object Manager
To benefit from the latest functionality available in this version of MicroStrategy Object Manager, an administrator must upgrade the MicroStrategy system, including Object Manager and Intelligence Server:
- MicroStrategy products 10.4.x and 2019 and above can be upgraded directly to MicroStrategy ONE or MicroStrategy 2021.
Before upgrading, see the Upgrade Help for important information about preparing for the upgrade, the order in which to upgrade products, and tasks to perform after upgrading.
Uninstalling MicroStrategy Object Manager
For details about uninstalling MicroStrategy Object Manager, see the Adding or Removing MicroStrategy Components chapter of the Installation and Configuration Help.
For a list of all the resolved issues in this MicroStrategy release, see Resolved Defects and Enhancements.
Troubleshooting Known Issues
Issues that have a prefix of S (S#####) are customer cases that can be tracked through MicroStrategy Technical Support. Those that are prefixed with T (T#####) are MicroStrategy internal issues. Internal issue numbers do not correlate to customer case numbers.
- T333899 - If you attempt to move or copy a report, and the attribute forms of an attribute used in that report are different between the source and destination projects, Object Manager will not allow you to move the report.
Workaround: To resolve this conflict, look at the report's dependents in the source project, and find the attributes that are in conflict. Migrate these attributes to the target project with the Replace action. You can then migrate the report.
- It is not recommended that you open two instances of Object Manager on the same machine connected to the same project. Locking conflicts will occur.
- The destination project must be of the same or greater metadata version as the source project. Operations cannot be performed from a newer metadata to an older one. The destination project must be updated first.
- In the MicroStrategy architecture, each object is identified by its unique Object ID. MicroStrategy Object Manager functionality is based on the Object ID. Therefore, objects with different names in related projects could potentially be related if they have the same Object ID. This occurs when an object is individually copied from one project to another or is duplicated as part of the project duplicate operation and the name of either object is then changed.
- If a project, for example, Project B, is a duplicate of an original project (Project A) and Project B is duplicated to create Project C, Project C is compatible with Project A for Object Manager use.
- In order to maintain a simpler production and development environment, it is recommended you move the initial MDX cube reports from development to production before creating any in the production environment.
- The preference option for table mapping has been removed. The original mapping of the source object will be maintained in the destination project.
- Project comparison does not support objects for MDX cube sources.
- Object Manager logs can be configured using the MicroStrategy Diagnostics and Performance Logging tool. These logs are part of the Source Manipulator dispatcher, within the component Client Services.
- Sample xml files for creating and importing project and configuration packages from the command line are provided in the Object Manager installation folder.
- When importing project security packages, the associated configuration package must be imported prior to importing the project security packages.
- Force Replace and Delete actions are available only for packages, to handle complex migration scenarios, and not for conflict resolution using Object Manager.
- Using the Project Comparison Wizard, you can synchronize folders between source and destination projects. Objects that are present only in the destination project can be selected for removal, except for any objects in the destination project which is a dependent object of other objects in the destination project.
User Merge Wizard
- The automatic mapping feature pre-selects users and groups with redundant names, such as DSSADMIN and DSSADMIN1.
- The Project Merge process locks both the source and destination projects by default. While this default behavior can be changed, it is recommended to lock the source and destination projects for all project merges.
- The results of a specific object, particularly the parent and child relationships of attributes, depends on the resolution of all the related attributes.
- Selecting the Keep Both setting for both the report and metric contained in the report results in a copy of the parent (the report) pointing to the original child (the metric). The copy of the child will not be used by the parent.
- Projects must have the same Schema ID and they must be updated to the same metadata version prior to the merge.
- The destination project must be of the same metadata version or older metadata version as the source project. Operations cannot be performed from a newer metadata to an older version. The destination project must be updated first.
- To run multiple project merges from the command line, add <SkipProjectMergeSourceLockingSkipProjectMergeDestConfigLocking> under OMSettingsOnOff in the Project Merge XML and make sure that the Project Merge Log file names are different in each Project Merge XML or multiple Merge sessions will not start.
- Undo functionality is not available.
- Project Merge logs can be configured using the MicroStrategy Diagnostics and Performance Logging tool. These logs are part of the Source Manipulator dispatcher, within the component Client Services.
- Force Replace and Delete actions are not available for objects in the Project Merge wizard.
Repository Translation Wizard
- When using the Repository Translation Wizard, the translation import process does not change the object version ID and modification time of any objects that receive updated translations.