Benefits of the New Model Merge Behavior

DaVinci Configurator uses a priority-based model merge with conflict detection and reporting. This topic explains why DaVinci Configurator works this way 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 silently. As a result, inconsistent data could stay unnoticed until a later project step or until the generated output no longer matched your expectations.

The current model merge detects and reports these situations during project load. These are not new issues — they already existed in the project but stayed invisible. Making them visible benefits everyone, because you can now find issues early, fix them systematically, and trace them in the report.

Improved Transparency

Because DaVinci Configurator explicitly detects and reports conflicts, you can see exactly when and where they occur. This makes project behavior easier to understand, especially when several ARXML files contribute to the same AUTOSAR element.

Traceability of Values

You can trace every value in the in-memory model back to its source files and their priority.

When Automatic Conflict Resolution is active, the SARIF report documents which value was chosen and from which file it came. This gives you a clear audit trail for every resolved conflict.

Complete Overview of Errors

In DaVinci Configurator Version 5, any serious project error could abort project load immediately.

The new behavior collects file-based issues during project load and presents them in one complete report at the end. This lets you fix multiple issues in a single iteration instead of resolving one issue and reloading the project again and again.

Line-Based Report (SARIF)

DaVinci Configurator writes all detected conflicts to a SARIF report in Output/Log/ProjectLoad/ inside your project.

SARIF (Static Analysis Results Interchange Format) is an OASIS open standard. As an open standard, it offers these advantages:

  • A wide and growing range of editors, CI systems, and tools support it natively.

  • You can view the results in your preferred editor or toolchain.

  • If no existing viewer fits your workflow, the open standard makes a custom solution easier to build.

For details on the structure, format, limitations and the recommended way to read the report in VS Code, see Model Merge Report.

New Error Resolutions

In DaVinci Configurator Version 5, certain conflicts during project load could not be resolved at all and stopped project load.

The new behavior reevaluates many of these previously blocking situations and covers them with automatic resolution logic. As a result, DaVinci Configurator 6 often needs fewer manual fixes for ARXML problems.

For traceability, DaVinci Configurator marks all automatic resolutions in the SARIF report.