Introduction:
When I try to perform Cross Project Merge selecting a package containing a “D”-tagged folder, SCM prevents it with a message like this:
---------- Begin <Cross Project Merge> Process ---------------
E03020691: Cannot merge path because sub item/path under path : \Sample Repository\TESTDATA will be lost after merged.
E03060019: Process Execute failed. Process Name: Cross Project Merge.
---------- End <Cross Project Merge> Process ---------------
Question:
Why would a Cross Project Merge result in a E03020691 error and prevent this merge from completing?
Environment:
Harvest Software Change Manager, Versions 12.0 and above, all platforms
Answer:
When a Cross Project Merge is performed, selecting a package that contains a "D"-tagged file, the corresponding file in the target project will also receive a "D"-tag:
<Please see attached file for image>
If SCM were to allow a Cross Project Merge selecting a package that contains a "D"-tagged folder, it would mean that the corresponding folder in the target project would also receive a "D"-tag. If that folder in the target project were to contain any files not found in the source project, those files would also be "D"-tagged and become invisible:
<Please see attached file for image>
To prevent this possible unintended consequence, SCM will return the error message and the Cross Project Merge will not succeed.
The only exception to the rule is if the same folder in the target project also has a "D"-tag. In this situation the Cross Project Merge will succeed:
<Please see attached file for image>
The other possible ways to make the Cross Project Merge to succeed are:
Additional Information:
Additional information about how Cross Project Merge works can be found in the CA Harvest Software Change Manager Workbench User Guide, chapter 11