Keep local chages when importing changes from earlier exported Model

[berch33]

Hi,
I seem to be incapable of using the "Ex-/Import-XML" merge feature. I rtfm, I tried different scenraios, I failed. Documentation does not cover a Sequence example on when to do what with which file.

If you know of such, please tell me. If not, maybe you can show me where my error further down. Anyway, thanks for reading!

>> I cannot make the merge run whatever files I use<<

Link to the Sequence Picture
https://bit.ly/32gFGAn

[qwerty]

You need to focus on the very same package you want to import as to where it had been exported. E.g. if you exported package A you need to call the import from the context menu of A and not somewhere else. And of course you must not change the focus inside the import menu.

And at no place you must use "strip GUIDs".

q.

[Geert Bellekens]

I would strongly suggest to find another way of working that doesn't involve the need to merge models.
Out of the box that is not really possible with EA.
I have been at many different clients so far, and we never had a situation that really required merging.

If you really don't have any other choice then you might want to look into LemonTree from LieberLieber.
But don't expect a free lunch. Merging model is a complicated and time consuming (and thus expensive) task regardless of the tools used.

Geert

[berch33]

Hi, thanks for the answers.
I found a way to do this, but it does not involve the "import --> merge" Buttons...

• Export the model
• They change model
• We change model
• we baseline
• we import their changed model and overwrite our model changes
• Now we "Show Differences" against our last baseline
• Merge editor shows all our changes --> select all --> import form Baseline
• Now the current model contains all "our changes" merged with "their" newly imported model

Works, tested. Will probably become a pain over time as differences will grow...

I asked EA support how they expect the "Import-merge" to work, but they only point to documentation, which is practically useless in this particular point...

[qwerty]

But that's the way to do it. If you decided to do it that way. The better would be to get your model split in such parts that you can work independently (as fas as possible). Much more efficient would be to look for ways to share a common database.

q.

[berch33]

... Much more efficient would be to look for ways to share a common database.

Of courcse we use a DBMS! But rules do not allow externals direct access to it... So we have to Export the model for them... they then develop it further and send an export of it back to us repeativly... Now we have to merge their model with ours.
They, of course, have their own ROOT model within the DBMS, as we have ours. But we work with elements of within their Root model in our model: add connections, for example. Those are all gone if we import their model.
This is why we have to merge.

Btw: when "this" (Baseline/Import/Merge) is THE WAY to do it right, what is the function "import --> merge" for then? Couse when would you use it, if not in our situation?

Chris

[qwerty]

EA has lots of bells and whistles. Well, lots and lots you can simply ignore. Some just mislead you. Many are "me too" features. Still, EA has lots of good features. Many again are hard to find. EA is very unique :-/

q.