MDG Tagged Value Connector Limiting to One Stereotype

[Lefty]

Hello,
I am having problems with the tag value connector in my MDG technology. I am trying to use the same tag value name that connects two different stereotypes to two other different stereotypes. However when I import the MDG it only lets me select objects of the first stereotype for all uses of a tag value with the name.

An example will hopefully make it more clear:

Stereotype 1 (<Node>) of a Class uses the tag value connector to create a tag value called "Owner" that links to Stereotype 2 (<Organization>) for selection.

Stereotype 3 (<Document>) of a Class uses the tag value connector to create a tag value called "Owner" that links to Stereotype 4 (<Role>) for selection.

However, the "Owner" tag values on <Document> objects only let me select objects with the stereotype <Organization>.
How can I make it so that "Owner" tag values on <Document> objects will let me select <Role> objects?

[Lefty]

As a temporary solution I have created a custom tagged value that allows for the selection of either stereotype and not use tag value connectors at all:

Tag Name: Owner

Type=RefGUIDList;
Values=Class;
Stereotypes=Organization,Role;

This does allow me to select and <Organization> or <Role> for the tag value for both <Node> and <Document>.
While this is not ideal it is preferable to not being able to select a <Role> at all for a <Document>.

If there is a way to make it so I can only select an <Organization> for a <Node> and only a <Role> for a <Document> with the same tag value name I would much prefer that.

[qwerty]

Not sure how you did that, but the TV from each stereotype do not depend on each other.

q.

[Paolo F Cantoni]

Not sure how you did that, but the TV from each stereotype does not depend on each other.

q.

To echo qwerty,
I think you have two different versions of the same named tagged value: Owner.  If you want one (same-named TV) then your solution is the only one available.

If, on the other hand, you have TWO TVs NodeOwner and DocumentOwner then you can specify more precisely (target restriction) what you want.

Of course, elsewhere you need to associate both specific instances of Owner with the generic Owner concept.

HTH,
Paolo

[Lefty]

I think you have two different versions of the same named tagged value: Owner.  If you want one (same-named TV) then your solution is the only one available.

Thank you. I guess that is the solution I am going with then.