Enhancement
Major
Detail
Major
Detail
Bugfix
Detail
#26804
No consistent deletion of model elements during model upgrade
If, when booting a new software version with a new model version, it is detected that a model element is to be deleted, this deletion is carried out as part of the automatic data migration.
If an entire type including a reference to another type is deleted in the process, the association to which the reference is mapped remains in the dataset. Normally this has no harmful effects, but if afterwards an attempt is made to create the same type (with the same name) and a reference with the same name again, this fails with the error message that the corresponding association already exists.
Test
- Create application.
- Create module M` with types `A and B` and a reference-valued attribute `ab in A` pointing to `B`.
- Transfer the module to the IDE.
- Shut down the application.
- Reboot the application and shutdown again.
- Delete type A from the model definition in the IDE.
- Boot application.
- Expectation, type A does not exist any more.
- Shut down the application.
- In the IDE, recreate type A with its reference to 'B'.
- Start application.
- Expectation: Type A` exists again and has a reference to `B again.