[Solved] MDG TaggedValue Association filter

[Hermelin]

Hi,

I have an MDG with two stereotypes, EnterpriseVision and EnterpriseGoal, both extending the metaclass Class.

From EnterpriseVision there's an association <taggedValue> called goals that points to EnterpriseGoal. I want to tag a EnterpriseVision with links to several EnterpriseGoals.

I have this set up and if I create a EnterpriseVision a taggedValue named goals is there, and I can press a button in the value field that open a ConstructPicker, which allow me to choose elements form the model.  The problem is that the filter in the ConstructPicker is set to only show elements with stereotype EnterpriseVision and I'm thus not able to select any EnterpriseGoal.

Is it possible to change something in my MDG to set the filter to EnterpriseGoals instead?

Thanks for any input!


EDIT: According to Sparx the issue happens since I had named the association, not just the target role. "In earlier versions of EA the connector name was used for defining "Classifier" tags, however this feature has since been deprecated."

[KP]

If you open up your profile in a text editor and search for "EnterpriseVision" you should be able to find an occurrence of that string that you can change to "EnterpriseGoal" (you'll know which occurrence to change when you see it - it will be in a <TaggedValueType> definition).

To figure out what is going wrong with your profile generation might be more difficult, but check that you don't have more than one «taggedValue» association between your "EnterpriseVision" and "EnterpriseGoal" stereotypes.

[Hermelin]

Thank you. I found the line. I have confirmed that I do not have a double connection.

After having tried all different ways of creating such associations, directions, combinations of source/destinations etc I noticed that I can make it change by changing the name of the stereotype.

EnterpriseVision -> EnterpriseGoal  ( Filter: EnterpriseVision)
EnterpriseVision -> EnterprisezGoal (Filter: EnterpriseGoal)

Thinking it could be dependent of some sort of alphabetic ordering I created new stereotypes named A-D. But it did not hold true for them.  Until, I tried changing the order in the project browser...


Can anyone confirm that what determines which stereotype is used for the filter is dependent on the position in the project browser, where a position lower in the list get priority? Is this an intentionally design?

[KP]

That sounds like a bug that was fixed in EA 8.0.859. Is your version of EA older than that?

Just to confirm, in EA 10.0 you create a «taggedValue» association from the «stereotype» that will have the tagged value to the «stereotype» that will be the results filter. Name the Target Role of the association to define the name of the tagged value.

[Hermelin]

I'm using EA 10.0.1009 (UE) and I do create the association the way you describe it. It is still the position in the browser that override the filter setting. I guess that turned this into a bug report.

Btw good thing you said to name the Target Role, since that activated the Multiplicity, which I was also wondering why it didn't work.

[Hermelin]

I have submitted it as a bug. I could live with it by placing the elements correctly, but this do not work when the connected elements are in different package.


EDIT: According to Sparx the issue happens since I had named the association, not just the target role. "In earlier versions of EA the connector name was used for defining "Classifier" tags, however this feature has since been deprecated."