Rename layers
1. Describe the Problem
ModelCHECK currently supports a "Layer Move" function that, for legacy parts, can create new layers, move items from old layers to the new ones, and delete the original layers. However, this process can disrupt existing layer states, causing unintended display issues. A solution is needed that allows ModelCHECK to rename existing layers—rather than recreating and deleting them—to preserve current layer states.
2. Are you using a workaround?
We are currently using mapkeys that require users to manually select the layer to be renamed. This approach is time-consuming, error-prone, and inconsistent across users.
3. What is the use case for your organization?
Our organization relies on layer states for both Model-Based Definition (MBD) and drawing documentation. To maintain consistency and avoid display issues, we need the ability to rename legacy layers without affecting existing layer states. This ensures that MBD views and drawing representations remain intact while updating layer naming conventions.
4. What impact does this problem currently have on your organization?
The current limitation in ModelCHECK impacts our ability to efficiently update legacy models while preserving critical layer states used in MBD and drawings. The manual workaround using mapkeys introduces inconsistencies, increases the risk of user error, and adds unnecessary time to the process. This reduces productivity, complicates standardization efforts, and may lead to incorrect model visualization or documentation if layer states are unintentionally altered.
