Synchronization Issues

[ola_strandberg]

Please can someone from Sparx describe the intended behavior and explain the below?

We do multi-developer work by version controllíng a model master. Each developer has a replica and synchronizes changes periodically.

Yesterday, I illustrated how to add the next level of detail to sequence diagrams that we have already defined. I then deleted the objects/messages that I had created.
Afterwards, dev1 and dev2 (names withheld ;-)) sat down together and did some testing on dev1's PC, deleting everything, and doing it "live" on dev2's PC.

At the end of the day, we all synchronized the model. We ended up with a sequence diagram that contained all our changes, including the ones that each of us had deleted! It also included two occurences of the same object, something which can not be done manually. Also, there were a number of replication conflicts on "Modified Date" attributes of elements.

Grateful for explanations and tips.

Cheers,
Ola