Edit a complex library structure
If updating a library version requires a series of invalid interim changes to accomplish the desired final result, you must lock the parent version before making the changes.
- Refactor
- Remove from
- Update to
- Create new instance
- Add to
For example, when the version is locked, users cannot add an object such as a topic to the version or remove it, but can edit the topic or add it to a map already in the version.
Once the version is locked, you can perform the operations needed to accomplish the desired final result, and then you release the version. Before the changes are released to the repository, the final results are verified for:
- Version conflicts
- Key changes
- Invalid objects
- Status changes
If any errors are discovered, a dialog box displays the issues that must be resolved before the release can proceed. If no errors are found, all versions affected by the changes are locked, all the changes are applied including status changes and key changes, and the container is updated.
When you need to use the Library Dependency Editor to perform a
series of invalid interim changes to accomplish a desired final result, you must
look at the changes you need to make and identify the parent version common to all
the versions being edited and open that parent as the focus library in the Library
Dependency Editor. For example, in the following figure the parent version
containing the proposed changes is the Prod Y v1
version and, therefore, should be opened in the Library Dependency Editor as the
focus library.
To lock a version: