MicroStrategy ONE

Update Projects with New Objects

When you create or modify an object in your development environment, you eventually need to copy that object to the test project, and later to the production project.

For example, a developer creates a new metric in the development project. Once the metric is ready to be tested, it needs to be present in the test project. You could re-create the metric in the test project based on the same specifications, but it can be easy to miss an important setting in the metric. A quicker and more reliable method is to use MicroStrategy Object Manager to migrate the new metric from the development project to the test project. Then, when the metric is ready to be rolled out to your users, you can use Object Manager again to migrate it from the test project to the production project.

MicroStrategy has the following tools available for updating the objects in a project:

For a comparison of these tools, see Compare Project Merge to Object Manager.

  • If you want to move or copy objects between projects, MicroStrategy recommends that those projects have related schemas. This means that either one project must be a duplicate of the other, or both projects must be duplicates of a third project. For information about duplicating projects, including instructions, see Duplicate a Project.
  • If one of the projects is updated to a new MicroStrategy release, but another project is not updated, you cannot move or copy objects between the projects. You must first update the other project before you can copy objects between the projects.