Discard a Document From A Project Folder

• Discarding a project copy from a project folder is similar to, but different than, deleting a project copy from the project folder. They both delete the project copy and unlock the master document. But deleting the project copy breaks its incoming references whereas discarding the project copy reroutes its incoming references to the master document and maintains the referential integrity of the related documents. For this reason, you should always discard project copies, not delete them unless you know that no incoming references will be broken.
• By default, this action also removes any references to the discarded project copy. However, this behavior can be configured differently by a system administrator. Depending on how it is configured, references between project copies might be redirected to the master document if a project copy is discarded from the project. If the remaining project copy is released from the project, both master documents will then be related by a reference that did not exist prior to the project copies being made. In some scenarios, such as assembly relationships, this might be desirable. In other scenarios, this might not be desirable. Before using this command, carefully consider its effect on references with respect to your business processes and consult a system administrator if the result is uncertain.

To perform this task, you must be a member of group that is assigned to the Project Owner or Tenant Administrator role that is assigned to the parent folder.