Tag values mixing groups (ver 13.0)

[Mauricio Moya (Arquesoft)]

I have a MDG containing profiles. I created a stereotype called "Application" and another one called "Platform", both extend Component metaclass. Both have the same tag values, and the tag values are organized in groups (as both extends the same metaclass, the groups definitions is in the single metaclass element).

I have made several versions of the MDG (every 3 months it happens an update), so I have different elements in different versions of the profiles. The situation about versioning is similar as described here: https://www.sparxsystems.com/forums/smf/index.php/topic,39829.msg245210.html#msg245210

Then, I changed some elements, changing their stereotypes from Platform to Application. To do so, I have a script that allows to do it for a large number of elements simultaneously, selected from a diagram.

After doing that (and experimenting some issues as described in the post of the link above), I manually "fix" the data in the stereotype, and in the t_xref table. It seems to be simple: I had to erase the reference to the Platform stereotype in the t_xref row related to "Stereotypes" and I noted that there is a row in t_xref related to "CustomProperties" containing the tag grouping definition for the element. As the two profiles has the same tags and groups, it is not required to change the t_xref CustomProperties data (there is no reference in this rows related to the profile name.

So, the issue is: after changing the stereotype of the element, the tag grouping is showing the tag values grouped in a weird way, like this:

ProfileName::Platform
-Group A
--Tag 1
--Tag 2
--Tag 3
-Group B
--Tag n
--Tag n1
--Tag n2
ProfileName::Application
--Not grouped tags

What is expected:

ProfileName::Application
-Group A
--Tag 1
--Tag 2
--Tag 3
-Group B
--Tag n
--Tag n1
--Tag n2
--Not grouped tags


The Description in the t_xref for this cases is: @STEREO;Name=Application;FQName=ProfileName::Application;@ENDSTEREO;
(previously it had two definitions of @STEREO (one for Application and one for Platform), so I fixed it manually directly in the database)

[Paolo F Cantoni]

I've noticed something similar.  It may be just a lack of consistency enforcement (happened a few years ago, IIRC).

It is irritating.

However, it may just be Sparxian Consistency versus User Consistency. "It's consistency, Jim.  But not as we know it..." 

BTW: Is it reproducible?  If you put the original stereotype back, does it revert and then revert again as you put the new stereotype back?

Paolo

[Mauricio Moya (Arquesoft)]

BTW: Is it reproducible?  If you put the original stereotype back, does it revert and then revert again as you put the new stereotype back?

Paolo

It worked! the solution is:
1) Apply the undesired stereotype by drag&dropping from the Toolbox pressing Ctrl over the conflicting element.
2) Uncheck the desired stereotype from the checkboxes in the Stereotype attribute of the element. At this point, the tag values are all grouped in the wrong stereotype group, but are all in the same group.
3) Apply the desired stereotype by drag&dropping from the Toolbox pressing Ctrl.
4) Uncheck the undesired stereotype from the checkboxes in the Stereotype of the element.

[Paolo F Cantoni]

It worked! the solution is:
1) Apply the undesired stereotype by drag&dropping from the Toolbox pressing Ctrl over the conflicting element.
2) Uncheck the desired stereotype from the checkboxes in the Stereotype attribute of the element. At this point, the tag values are all grouped in the wrong stereotype group, but are all in the same group.
3) Apply the desired stereotype by drag&dropping from the Toolbox pressing Ctrl.
4) Uncheck the undesired stereotype from the checkboxes in the Stereotype of the element.

Hi Arquesoft,

I thought yu had already done that procedure...  What you have defined is the standard process for manually redefining a metatype.  If you don't do the steps of making sure you have cleared the StereotypeEx properties (where you unmark the checkbox of the non-current stereotype) then EA doesn't recognise the metatype correctly (Ask me how I know?  )

Anyway good to see you've solved it.

My issue, I now recognise is not the same as yours, is that the order of the Groups seems to vary between metatypes even though the same groups might be involved.  But I'll do more checking.

Paolo

[Mauricio Moya (Arquesoft)]

I thought yu had already done that procedure...  What you have defined is the standard process for manually redefining a metatype.  If you don't do the steps of making sure you have cleared the StereotypeEx properties (where you unmark the checkbox of the non-current stereotype) then EA doesn't recognise the metatype correctly (Ask me how I know?  )

The reason I hadn't do that was there were hundreds of elements with that issue. I really was looking for a script (jscript or SQL) solution, but I really had to fix it by hand, one by one. They are now all fixed. But I still look for a script that has the same effect.