MDG Technology Tagged Value inconsistency

[Paolo F Cantoni]

I'm not sure if this is a Bug (EAUI) or I've mucked up something in my MDG technology profile specification.

I have an MDG Technology Name: TerminologicalModelling  ID: SME.TM
In that MDGT I have a tagged value GenerationalReferenceModel which is defined as:
Type=RefGuid;
Values=Package;
Stereotypes=ReferenceModel;

So I apply this stereotype to a number of the elements defined within the terminological model profile.
I create the toolbox and all appears fine so far.

When I create an element from the toolbox, sure enough, I get an element with the requisite tagged values (in t_objectproperties - on eof which is Property = GenerationalReferenceModel ). Or do I?
When I investigate the RefGuid tagged value above, I don't get the [...] builder button I expected on the tagged value.  It appears to be behaving like a string

However, if I use the Add tagged value button on the Tagged Value Window, I see: SME.TM::GenerationalReferenceModel - which is obviously the fully qualified Tagged Value name for the above MDG defined Tagged Value.
If I add THIS Tagged value to the element, I DO get the RefGuid [...] builder button - and a tagged value of SME.TM::GenerationalReferenceModel entry is added to t_objectproperties in addition to the (unqualified) GenerationalReferenceModel.  The qualified Tagged Value works properly and allows me to select the appropriate package from the repository.  The unqualified tagged value is as useful as the proverbial "tits on a bull".

 Looks like a case of: Concistency, konsistency, consistensy! ^TM_{Uffe - after Paolo}
 
 Can anybody explain what's going on here?
 Has anybody had a similar experience?
 Has anybody got the RefGuid to work off the toolbox?
 
 TIA,
 Paolo

[qwerty]

Sorry, but I'm a bit short of time right now. I guess you still remember this post?

I also had trouble with this RefGUID. Will look into it later...

q.

[Uffe]

Anyone mention my name?

The tagged value definition is case-sensitive. (But not sensitive enough to warn you...)

Code: [Select]

Type=RefGuid; and

Code: [Select]

Type=RefGUID; yield different results.

With the former, you get a drop-down list where you can select from the values (element types) you've specified and possibly enter a string as well. (Strictly speaking, this behavior is undefined.) With the latter, you should get the ellipsis thing.

And to paraphrase: Helpfully not reporting input errors ISN'T.  

HTH,


/Uffe

[Paolo F Cantoni]

Anyone mention my name?

The tagged value definition is case-sensitive. (But not sensitive enough to warn you...)

Code: [Select]

Type=RefGuid; and

Code: [Select]

Type=RefGUID; yield different results.

With the former, you get a drop-down list where you can select from the values (element types) you've specified and possibly enter a string as well. (Strictly speaking, this behavior is undefined.) With the latter, you should get the ellipsis thing.

And to paraphrase: Helpfully not reporting input errors ISN'T.  

HTH,


/Uffe

The spell checker got in the way... The tagged value IS specified as RefGUID.

I think the solution might be that pointed to by qwerty - I'll check it out and let everyone know...

Paolo

[philchudley]

Hi All

I had a similar problem when creating tagged values for MDG Stereotypes of type Memo

I have found the solution. Simply add a line similar to

[highlight]BaseStereotype=Class[/highlight];

(where Class is the Metaclass that is being extended in the profile)

to the TaggedValue definition

This worked for me

Give it a try

Cheers

Phil

[Paolo F Cantoni]

Sorry, but I'm a bit short of time right now. I guess you still remember this post?

I also had trouble with this RefGUID. Will look into it later...

q.

I tried Phil's work around and it didn't solve the problem.  I think he was talking about a different EAUI.

This one is about the inconsistencies of identity for what is the same tagged value and the consequences therefrom.

It seems this kind of problem is almost worth another Dear Geoffrey...

Paolo

[Paolo F Cantoni]

Sparxians,

Do I need to send in a Bug Report or is it a setup problem on my part?

TIA,
Paolo
[edit]Now reported[/edit]