create tagged value with specific FQName

[Pawel Jasinski]

hi,

I am trying to create tagged value with a given FQName. Is there a way to accomplish it without tinkering directly with t_xref content?

Has anybody figured out what exactly has to be inserted?

Cheers,
Pawel

[qwerty]

Unfortunately no. But if you figure it out I'd appreciate to have a little insight. Likely it's a bumpy road ahead of you.

q.

[Geert Bellekens]

You'll have to use Element.TaggedValues.AddNew() or is that not what you are asking?

Geert

[qwerty]

I guess no. Creating a Tag from an MDG is not done that way. There are some strange things happening behind the scenes.

q.

[Geert Bellekens]

Ah, I didn't read 'MDG" in the question..

Geert

[qwerty]

It's hidden behind FQ. AFAIK only MDGs are connected with FQ tags.

q.

[Geert Bellekens]

Ah, OK. My bad for not knowing anything about MDG

Geert

[qwerty]

Lucky you :-)

Makes me a bit wonder. You're joking, aren't you?

q.

[Geert Bellekens]

No I'm not.
If you look at my contributions you'll note that none of them are regarding MDG technologies.
It's an item on my todo list to familiarize myself with the MDG stuff.

Geert

[KP]

The FQ path of a tagged value is encoded in its GUID, and you can't change a GUID once it's been set. Therefore, it's all about how you create the tagged value: either create a stereotyped element so the tagged values are created automatically; or add a stereotype to an element and then synchronize it to add the tagged values. (In both cases you'll notice it's EA creating the tagged value, not you...)

[Geert Bellekens]

The FQ path of a tagged value is encoded in its GUID

Are you fricking kidding?
OMG, you should send that to http://thedailywtf.com/ I think that would make the frontpage

Geert

[qwerty]

Phew. Hard stuff indeed. That happens when you code for years without redesign or refactoring and you run out of trap doors.

q.

[Pawel Jasinski]

hi

Thanks for all the info. Somehow I am not getting any email notifications when replies are posted :-(

Anyway, what I have discovered hard way is exactly what KP says.
Here is the snipped from the db session which shows what happens when stereotype (with the right tagged values) is applied to existing element:

delete from t_objectproperties where Object_ID=12 and ea_guid like '{[highlight]D4F0310E-E861-2fe8[/highlight]-%' and Property='aNamespace'

Insert into t_objectproperties(`Object_ID`, `Property`, `Value`, `Notes`, `ea_guid`) Values(12,'aNamespace',NULL,NULL,'{[highlight]D4F0310E-E861-2fe8-B98D[/highlight]-E17A6212FB46}')

First all 'old' values from the compartment are nuked. Then the default one is inserted.
For a given tagged value and compartment the highlighted part of guid is always the same.

KP, is there a way to tell us how is the GUID generated?
Or perhaps some magic call into EA dll?

I have an idea for a workaround. For a given Model, I would have a dummy package with manually inserted elements. I can read the magic GUIDs out of the DB and (re)use when inserting new tagged values.
Anybody see a problem with this?

I also noticed something alarming. When I delete a tagged value out of compartment, I see no way to re-insert it using GUI? Until now I found only "apply <stereotype>", but this nukes all other values.
I also tried Compartment::Name. It gets into the right compartment but the name is inconsistent with the default name.

Cheers,
Pawel

[Pawel Jasinski]

> Somehow I am not getting any email notifications when replies are posted

It was a spam filter :-(