Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - José

Pages: [1]
Uml Process / Re: Re-using controlled packages resulting in erro
« on: October 06, 2015, 03:22:29 pm »
Thank you Qwerty,  the strip GUIDs did it...

Uml Process / Re-using controlled packages resulting in error...
« on: October 05, 2015, 09:27:43 pm »
Hi all,

I have a question regarding controlled packages. We have an EA model containing all generic requirements. These requirements are being used by other projects, which all have their own EA model. Since the projects want to re-use the generic EA model, we have placed all EA models under version control (root node > package control > add branch to version control)  using Subversion.

When I re-use the generic requirements into one of the project EA models (package control > get package), I get the error message “error: root import package already exists in another location”. It said that in my current model (with multiple model nodes, there is already a package with the same name. Since all our models are using the same layout, this is true. But I expected that since I placed the package in a new model node, it would work. But I also got the impression that all my EA models got the same GUIDs when being placed under version control and this might cause also the error.

Did anyone experienced this issue before? If so, how can this be solved but still keep using our standardized layouts for all projects?

Note that all our EA models are placed on the SQL-server, so there are no local copies. Also each EA model has the same standard layout. This means that each model has the same package structure and also the same package names.

Thank you in advance.

Kind regards,


Thank you to both... That's indeed what I am looking for.

Kind regards, José

Hi Geert,

I know that, but that's not what I meant. There is also the 'alias' field in which you can give the requirement a name like 'STK-001' or 'US-001' or whatever is determined within the organisation, which is visible for all EA users in your model. I was wondering if there is a way to get this field automatically filled with some value. We then can start referring to this alias in our documents so that everyone knows exactly about which requirement we are talking.

Hopefully this clarifies my question.

Kind regards, José

We want to put a lot (>1000) of requirements into our Enterprise Architect model. But these requirements do not yet have an unique identifier in EA, which is required. We do not want to give each requirement this ID by hand. Is there a way to auto-generate this ID for all these items in once?

I was thinking that maybe this might already be standard EA functionality. If not, could we otherwise use the scripting functionality?

I hoped to find some information on this online (user community/forum) but I was not able to. Does anyone have any suggestions/examples how they do it within there organisation?

Kind regards, José

Pages: [1]