NDMerge V2.0 Release Notes

2.0.2.50109

The tool has been updated with the upgrade to Next Design V4.0.

New Features

• When performing a merge (including pull, etc.) while mutually editing profile information, the changes of both are maintained as much as possible.
• When an inconsistency is detected when merging profile elements, it has been changed so that it is not merged as a conflict.
• When merging profile elements, the following are changed to be considered inconsistent.
• A parent-child relationship of packages is circular.
• A parent profile element no longer exists.
• There are multiple element view definitions corresponding to the same field.
• The referenced custom resource does not exist.
• It is now possible to check the difference information of model files that have been changed in hierarchy or renamed as a difference in the unit information of the project.
• Previously, if you changed the hierarchy or renamed a model file, the difference could not be obtained, but now you can check it as a difference in the unit information of the project.
• Changed to stop merging if the project data contains unit files with the same path but different TopElementIds.
• Previously, if you merged model files with different TopElementIds and made changes (hierarchy changes or renames) that made Own and Other have the same path, the model file after the path change was considered a conflict, but from now on, the merge will be stopped.
  In this case, the error [e9003] will be output to the log.
• It is now possible to merge if the major version matches even if there is a version update in the schema version of the Next Design file.
• Files with schema versions 11 to 13 (=schema versions up to V4) are targeted.

Fixed issues and restrictions

• Fixed the issue of merging moves and order changes when performing a merge (including pull) while profile information was being mutually edited.
• Improved to maintain collection order as much as possible when merging with NDMerge.