Issue with DataHub Sync

[userkhoa]

I set up DataHub 17.0.3 to talk to DOORS 9.3 and Enterprise MagicDraw 17.0.3. In my test case, I moved a requirement object in DOORS from one location of the hierarchy to another location. For instance, I promoted Requirement C from 1.2 to 2 in the hierarchy as laid out below.

Before change:
1 Requirement-A
__ 1.1 Requirement-B
__ 1.2 Requirment-C

After change:
1 Requirement-A
__ 1.1 Requirement-B
2 Requirment-C

After synchronzing the change in DataHub, the corresponding SysML requirement block/element was deleted. That was clearly erroneous. I executed sync again. The requirement element was recreated in the right hierarchy in the model. But since the original element was deleted, all its relations were also deleted. In other words, it did not actually move the original element and kept all links intact. Instead, it deleted the element and recreated it as a brand new element using the same requirement text and name. The same issue occured when I sync'ed the other way. For example, I moved the requirement element in my model and sync'ed the changes to DOORS database. After the first or second sync attempt, the original requirement in DOORS was deleted. Subsequent sync would create a new requirement object with a new absolute ID in DOORS. Can somone/NoMagic confirm this? Is there any fix/workaround? Thank you.

[supatp]

Dear userkhoa,

DataHub 17.0.3 do not support the synchronization for hierarchy changes yet. We plan to support this case in the next release 17.0.4 that targeted to release by early July 2013.
If the current behavior cause you trouble, what we can do is, provide you a patch. The patch will not support the synchronization for the hierarchy change, it will ignore the location changing, no re-create. The data will be synchronized as normal, but not the location.

Will the patch like this work for you?

Beat Regards,
Supat P.

[maxwell.yavaraski@ngc.com]

I am experiancing a similar issue in 19.0 SP3. When the hieracry changes it no longer deletes the element and recreates it but I get an error "Failed to Move" is there any work around for the Failed to move issue other than deleting the entire module and starting over?

Thank you,
Max