Sparx Systems Forum

Enterprise Architect => General Board => Topic started by: tim-southerland on November 02, 2010, 03:00:18 am

Title: what is the true impact of using "Strip GUID"?
Post by: tim-southerland on November 02, 2010, 03:00:18 am

In the "Import" dialog there is an option to "Strip GUIDs"   what will be the true impact of selecting this option?

Are elements mapped to each other by GUID? Are they indexed by GUID in the database?  What other impacts might I expect if I choose to "strip GUIDs"?

Title: Re: what is the true impact of using "Strip GUID"?
Post by: qwerty on November 02, 2010, 03:53:10 am

Each imported element is created with a new GUID as a carbon copy. No mapping to existing elements is done.

q

Title: Re: what is the true impact of using "Strip GUID"?
Post by: tim-southerland on November 02, 2010, 11:56:31 pm

The key question is "how are GUID's used before they are stripped?"  This will lead to a better understanding of the impact when they are removed or overwritten.

Does anyone know exactly?

Title: Re: what is the true impact of using "Strip GUID"?
Post by: Geert Bellekens on November 03, 2010, 06:23:34 pm

Tim,

The option "Strip GUIDs" doesn't actually strip the GUIDs, but creates new GUIDs for each imported element.
This means that you are effectively creating a copy of the model iso synchronising with the existing model.
The GUID's are used to uniquely identify the elements in the model. So different GUID means different element.

Geert