Lock Projects

When you open a project in Project Merge, you automatically place a metadata lock on the project. You also place a metadata lock on the project if you open it in read/write mode in Object Manager, or if you create or import an update package from the command line. For more information about read/write mode versus read-only mode in Object Manager, see Project Locking with Object Manager.

A metadata lock prevents other MicroStrategy users from modifying any objects in the project in Developer or MicroStrategy Web, while objects are being copied with Object Manager or Project Merge. It also prevents other MicroStrategy users from modifying any configuration objects, such as users or groups, in the project source. Locking a project prevents metadata inconsistencies.

When other users attempt to open an object in a locked project using Developer or MicroStrategy Web, they see a message that informs them that the project is locked because a user that opened the project first is modifying it. Users can then choose to open the object in read-only mode or view more details about the lock. Users can execute reports in a locked project, but the report definition that is used is the last definition saved prior to the project being locked.

If you lock a project by opening it in Object Manager, you can unlock the project by right-clicking the project in Object Manager, and choosing Disconnect from Project Source.

Only the user who locked a project, or another user with the Bypass All Object Security Access Checks and Create Configuration Objects privileges, can unlock a project.

You can also lock or unlock a project or a configuration manually using Developer.

Command Manager scripts can be used to automate metadata lock management. For information about Command Manager, see Automating Administrative Tasks with Command Manager. For Command Manager syntax for managing metadata locks, see the Command Manager Help (press F1 from within Command Manager).