Community
Participate
Working Groups
Let's take an odesign O1 with a page specification which uses a group A. Let's take an other odesign O2 which overrides the group A. If the group A is moved in O1, 02 loose the link to group A. So, the overriding group references an other group or a an unexpected description (causing error). Indeed, the id of the objects is dependent on their position inside the model.
Created attachment 282632 [details] Example on basicfamily On this example, you get GroupOverride from the extension.odesign which overrides DefaultGroup from test.odesign. This last one is used by the DefaultPage. If you move DefaultGroup to the top down (after DefaultGroup2) then it is DefaultGroup2 which becomes overridden (not used by DefaultPage).
Agreed, but this is a general issue with the VSMs, which could only be fixed by very deep and impactful changes in how their elements are identified. Unless it becomes blocking for very common scenarios *and* we find a way to fix it which is not too risky (in terms of compatibility especially), I suspect we will never be able to change this.
