Profile compatibility broken

[Frank Horn]

Just filed abug report (Build 861):

Details:

Tagged values pointing to a stereotype derived from object within a profile can not be assigned anymore.

Steps to Reproduction:

Create a profile with 2 stereotypes S1 and S2, extending metaclass Object. Draw a tagged value connector from S1 to S2 and assign a role name (say T1).

Pack it into an MDG technology and copy the mdg file to the appropiate directory.

Open a new instance of EA, activate the new technology, and create new objects of type S1 and S2. Try to set the T1 tagged value of the S1 object to the S2 object.

This used to be no problem in older versions of EA, when there was a list to select from. Now there is a tree view which does not show S2 objects.

This is very serious for us, because we cannot use our existing profiles. Existing models based on our profiles can not be edited anymore.

[Frank Horn]

Got an answer from support which gave me the crucial hint:

Can you please confirm that the name of your tagged value was applied
to the Role Name of the tagged value connector in your profile (and not
the name of the connector itself - this is known to cause issues)?

Indeed my tagged value names were applied to the connector name. I changed that now and named the target roles instead, and this solves the problem.

I seem to recall that at the time I set up the profile EA online help told me to put it into the connector name, which I thought was a little weird. Using the target role seems much more logical, so that's an improvement after all.