Benefits of the new Model Merge behavior
DaVinci Configurator uses a priority-based model merge with conflict detection and reporting. This section explains why this behavior was added and how it improves project handling compared to DaVinci Configurator Version 5.
Reason for Newly Reported Conflicts
In DaVinci Configurator Version 5, some conflicting ARXML definitions were merged without informing the user. As a result, inconsistent data could remain unnoticed until a later project step or until generated output no longer matched expectations.
The current model merge detects and reports these situations during project load. These are not newly created issues. They are conflicts that already existed in the project but were previously not visible. Making them visible is a benefit for all users because issues can now be found early, fixed systematically, and traced in the report.
Improved Transparency
The new Model Merge behavior explicitly detects and reports conflicts, so you can see when and where they occur. This makes project behavior easier to understand, especially if several ARXML files contribute to the same AUTOSAR element.
Traceability of Values
Every value loaded into the in-memory model can be traced back to its source files and their priority.
When Automatic Conflict Resolution is active, the SARIF report documents:
-
which value was chosen
-
from which file it originated
This provides a clear audit trail for every resolved conflict.
Complete Overview of Errors
In DaVinci Configurator Version 5, every type of serious project error could abort project load immediately.
The new Model Merge behavior collects file-based issues during project load and provides a complete report at the end. This makes it much easier to fix multiple issues in one iteration instead of resolving only the first visible issue and loading the project again.
Line-Based Report (SARIF)
All detected conflicts are written to a SARIF report in Output/Log/ProjectLoad/ inside your project.
SARIF (Static Analysis Results Interchange Format) is an OASIS open standard. Being an open standard means:
-
A wide and growing number of editors, CI systems, and tools support it natively.
-
You can use your preferred editor or toolchain to view the results.
-
If no existing viewer fits your workflow, the open standard makes it easier to implement a custom solution.
Please refer to Model Merge Report for more information on structure, format and limitations of the report. See How to Open and Use the SARIF Report for Model Merge Conflicts for the recommended way of reading the report with VS Code.
New Error Resolutions
In DaVinci Configurator Version 5, certain conflicts during project load could not be resolved at all and caused errors that stopped project load.
With the new Model Merge behavior, many of these previously blocking situations have been reevaluated and covered by automatic resolution logic. As a result, DaVinci Configurator 6 often requires fewer manual fixes for ARXML problems.
For traceability, all automatic resolutions are marked in the SARIF report.