Sparx Systems Forum

Enterprise Architect => Bugs and Issues => Topic started by: PeterHeintz on March 26, 2019, 08:08:05 pm

Title: Element Author not equal t_object Author
Post by: PeterHeintz on March 26, 2019, 08:08:05 pm
I created elements in an eap repository with neither security enabled nor model authors inserted.
In this case EA sets the element author to my Windows user account.
Because of I want to import those model fragments to another repository with security enabled, I try to change the author in the original EAP file to my user name in the security enabled target repository.
This works for most elements and all elements show the Author as expected. However for ports in ports when doing an element query or looking in the eap file directly, my windows account value is still in t_Object:Author.
Any comments on this strange thing?
Title: Re: Element Author not equal t_object Author
Post by: qwerty on March 26, 2019, 08:50:46 pm
Hmm. Reporting a bug sounds reasonable. If it's helpful would be questionable, though. You probably need to do some script fix-up.

q.
Title: Re: Element Author not equal t_object Author
Post by: PeterHeintz on March 26, 2019, 11:05:49 pm
Well, I changed the author by a script.
The really strange thing is that the elements properties show what I expect, but in the DB is something different, at least for ports in ports!?!?
So there must be a magic place, maybe in an XML fragment in a DB field which holds other author information instead if t-object.author which might be used for ports in ports.
Title: Re: Element Author not equal t_object Author
Post by: qwerty on March 27, 2019, 02:52:15 am
Unfortunately I do not have any security enabled repo for testing at the moment, so I can't test that. You should probably contact Sparx support via mail to see what their opinion is.

q.
Title: Re: Element Author not equal t_object Author
Post by: Eve on March 27, 2019, 12:30:58 pm
... However for ports in ports ...
These are a special case, in that they are required for EA diagram rendering only. They correspond to a port of the top level port type, and they can't be edited because they load directly from the referenced port.