RefGUID Tag behaviour different for profile vs UML Types

[Paolo F Cantoni]

We have defined a RefGUID Tag thus:
JurisdictionalLocationReference

Code: [Select]

Type=RefGUID;
Values=Class;
Stereotypes=Cntry;
Default={4D8BF378-485E-442f-BDB7-AADC6AF007FB} ;«Uninitialized»
We then use this definition in our MDG thus:

Code: [Select]

<Tag name="JurisdictionalLocationReference"  default="{4D8BF378-485E-442f-BDB7-AADC6AF007FB}"/> <!-- "«Uninitialized»" -->
As will be seen, we don't specify the type of the JurisdictionalLocationReference tag in the MDG.

If we create an object of the appropriate metatype from the toolbox, all is fine and the RefGUID returns the target value.

However, if we add the JurisdictionalLocationReference to another item (from UML types), we just get what seems to be a "string" with the value of the GUID clearly visible.  Once you change the value (via the [...] builder button) you get the appropriate dialog and thence all is as one would expect.

Reported,
Paolo

[Eve]

Your tagged value definition has a tab as part of the default value which is breaking it. (Because the default isn't a guid)

[Paolo F Cantoni]

Your tagged value definition has a tab as part of the default value which is breaking it. (Because the default isn't a guid)

Sure does!  My bad!     Typo and "Snow Blindness"!  All good now!

Thanks,
Paolo