Merge EAP File or Diagrams

[AndTheWinnerIs]

Hi,
it would be great if I could copy a Diagram from one EAP File to another. For example a newer Version of an EAP File was made in parallel by a Teammember.  The colleague modified all Diagrams and I added a new one.
At the moment it is simply impossible to copy a complete Diagram from one File to another.
 
I did some workarounds with editing the XML export and then modified the IDs, but you get carzy if you have complex Diagrams and Projects  

[Christian Herger]

Hi

I think it is not possible to just copy diagrams around EAP-files for all elements in a diagram are linked to objects in a project...

I suggest you start working with controlled packages and then all your team members use the same packages to work with.
If you even use some version control like SVN you prevent annoying package conflicts.

[«Midnight»]

Depending on your specific needs perhaps controlled packages would be enough.

Check out the white papers - particularly any dealing with version control or deployment of EA - on the resources page of the Sparx site.

[AndTheWinnerIs]

Controlled Packages is no solution because  I HAVE to use DocuShare as VersionControl
And I think EA is not supporting that VersionControl System.

I think it is not possible to just copy diagrams around EAP-files for all elements in a diagram are linked to objects in a project...

Why not copy these Elements also!? ...and if they are already present (checkable via the ObjectId, present in XML also) then use them.

[RoyC]

Read up on Baselines and Differencing in the Help. This enables you to selectively adopt changes in a Baseline in another iteration of your model into your current model. That is, you can't run the compare on a Baseline from a totally different model.

Let's say AndTheWinnerIs is called Fred. His colleague is Joe. Fred asks Joe to make a Baseline of Joe's version of the appropriate package.

Fred then runs a compare of that Baseline against that package in his current model. The compare identifies the differences (including Joe's changes) and Fred can selectively 'roll back' his model to include each of those changes.

Fred then makes a Baseline of his package, which includes the new diagram, and Joe then runs a comparison between the package in his current model and the Baseline from Fred's model. This detects the new diagram, and Joe can select that change to update his model.

Note that there is an option in the Baseline Compare to omit (supress) diagram changes in the comparison, so Fred and Joe would have to deselect this option.

HTH