Multiple records in t_xref table for one guid

[sravang]

Hello,

I don't exactly know why there are multiple entries for one guid in t_xref table.

I am trying to set stereotypeex and fqstereotype values from Description column in t_xref table.

I am using this query to get vaues - "select * from t_xref tx where tx.Client = '{0006EC54-FB51-4d5b-A141-7C9481571FD1}' AND tx.Name = 'Stereotypes'"

For this one it returns two rows with different Type one is attribute property and other is element property.

What exactly should be considered and what is the difference between them.

Thanks,
Sravan

[qwerty]

Then apparently you have assigned two stereotypes to the elemen.

q.

[sravang]

Is there anything to do with Type??

One record has type - 'attribute property' and other one has - 'element property'


Thanks,
Sravan

[Paolo F Cantoni]

Is there anything to do with Type??

One record has type - 'attribute property' and other one has - 'element property'


Thanks,
Sravan

Have you run a project integrity check?

That may clear up the issue.  Also, check if you have both an element with that GUID and an Attribute with the same GUID.

Paolo

[qwerty]

Is there anything to do with Type??

One record has type - 'attribute property' and other one has - 'element property'


Thanks,
Sravan

You then have an attribute in your element which is also stereotyped. Just use the element property entry for the element itself.

q.

[Eve]

One record has type - 'attribute property' and other one has - 'element property'

You then have an attribute in your element which is also stereotyped. Just use the element property entry for the element itself.

Not exactly, the 'attribute property' does refer to an attribute, but the Client should match a record in t_attribute.ea_guid. The Project Integrity check will pick that up and change the attribute guid. If there isn't one Project Integrity check should detect the orphaned row and remove it. If both types were the same the Project Integrity check will pick that up as a third type of issue, it would not mean that multiple stereotypes had been added to the element. (Seeing the pattern yet. Run Project Integrity Check)

[qwerty]

I was just writing out of my head (and having the feeling that it was not right). Also having seen Paolo mentioning the "usual suspect". It should be noted though, that the PIC needs to be run with the Repair option turned on and ignoring EA's warning that it's bad to do that :-/ (no, it isn't).

q.

[Paolo F Cantoni]

One record has type - 'attribute property' and other one has - 'element property'

You then have an attribute in your element which is also stereotyped. Just use the element property entry for the element itself.

Not exactly, the 'attribute property' does refer to an attribute, but the Client should match a record in t_attribute.ea_guid. The Project Integrity check will pick that up and change the attribute guid. If there isn't one Project Integrity check should detect the orphaned row and remove it. If both types were the same the Project Integrity check will pick that up as a third type of issue, it would not mean that multiple stereotypes had been added to the element. (Seeing the pattern yet. Run Project Integrity Check)

Thanks for clarifying, Eve,
I was hoping the PIC would fix that kind of thing, but never having had the problem myself (because I run the PIC early and often - like voting ), couldn't vouch for it.

Paolo