Release a Project Copy as a New Master Document
Releasing a project copy as a new master document causes a new revision of the master document to be created from the content of the project copy that is being released. The project copy remains in the project for future reference, though inactive.
To perform this task, you must be a member of group that is assigned to the Document Controller, Project Owner, or Tenant Administrator role that is assigned to the parent folder.
In order to release a project copy as a new master document, the following conditions must be met:
- The project copy must be in a released document workflow state.
- The master document must not be locked or it must be locked by the project copy being released. If the project copy cannot be released as a new master document revision because the master document is locked by a different project copy, you must unlock it first. See Unlock a Master Document.
- The master document must not have been changed since the project copy was created. If the project copy cannot be released as a new master document revision because the master document has been changed, you must reconcile the project copy with the master document first. See Reconcile With an Updated Master Document.
- In Meridian 2021, after project a copy is released, another project copy can be created from same master document in same project. You can create a workaround for this using VB Script.
- Master document hybrid parts will not be replaced by renamed project copy hybrid parts as expected unless the content of the project copies has also been changed.
-
You must have the following privileges to use this command if the master document already exists:
-
Document privileges: Edit in Application, View Content, Release as Master Revision, Lock Master Document, Update Master Document, Unlock from Project
-
Folder privileges: List Content
-
Workflow privileges: Start Quick Change, Release Quick Change
If the master document does not already exist you must have the following privileges in addition to the preceding privileges:
-
Folder privileges: Create Document
For more information about privileges, see Security privilege descriptions.
-
- If this command is run on a selection of documents, only the documents that meet the preceding conditions will be released. The other documents will not be released until the conditions have been met and the command run on them again.
To release a project copy to master:
- Do one of the following:
- Right-click the project copy then select Project > Release as Master Revision in the context menu that appears.
- Select the project copy then in the Project ribbon Assign group, select Release as Master Revision.
A new revision of the master document is created using the project copy.
If the document type is configured to use waiting lists, the Master and Project Copies page no longer shows that project copy. Depending on the way in which your vault and project folders are configured, the next waiting project copy remains as a waiting project copy. If this occurs, you can Transfer to next, which activates next waiting project copy and sets its priority to zero.
If the following conditions are true and you cancel the operation, the document will be released unexpectedly. If these conditions are not true, the document will remain its current state.
- Site cache mode option is enabled as described in Personal Preferences
- The document uses a custom workflow
- A custom property page is shown during the transition
To release a project copy to master in PowerUser:
- Select the project copy to be released.
- From the Document menu, select Managed Change (Master/Project Copy) , and click Release from Folder (Release as Master Revision). A new revision of the master document is created from the content of the project copy and the project copy becomes inactive.
