Skip to main content

Conflict Resolution Examples

This page demonstrates how SyncNow handles data conflicts during bidirectional synchronization, using different conflict resolution strategies. Understanding these scenarios will help you configure conflict resolution to match your business needs.

Scenario Details

Consider an entity pair where fields are synchronized bidirectionally, and initially, both entities have the same content. Let's explore different conflict resolution scenarios.

🟢 Initial State

Both entities start with identical content.

1

🔄 Bidirectional Synchronization

Synchronization is set up to allow updates in both directions.

2

🅰️ Scenario A – System A Wins

In this scenario, the conflict resolution setting prioritizes updates from System A.

  1. Initial Update
    Titles of both entities are updated before the next sync run.
    A1

  2. Post-Synchronization State
    After synchronization, both entities have content from System A.
    3

  3. Synchronization Status
    The status of the synchronization is Success.
    A3 Status

🅱️ Scenario B – System B Wins

Here, the conflict resolution setting prioritizes updates from System B.

  1. Initial Update
    Titles of both entities are updated before the next sync run.
    B1

  2. Post-Synchronization State
    After synchronization, both entities have content from System B.
    B2

  3. Synchronization Status
    The status of the synchronization is Success.
    B3 Status

❌ Scenario C – Throw an Error

In this scenario, conflicts result in an error due to the conflict resolution settings.

  1. Initial Update
    Titles of both entities are updated before the next sync run.
    C1

  2. Post-Synchronization State
    Titles of both entities are not updated due to the conflict.
    C2

  3. Synchronization Status
    The status of the synchronization is Partially Success. The Status Errors button will open the Status Errors page with details.
    C3 Status

  4. Error Details
    There are 2 sync errors.
    C4 Status Errors

📝 Summary

SyncNow provides flexible conflict resolution options to manage how data conflicts are handled during synchronization:

  • System A Wins: System A's changes take precedence.
  • System B Wins: System B's changes take precedence.
  • Throw an Error: Conflicts are flagged for manual review.

By setting up conflict resolution preferences, you can ensure your data remains consistent and accurate according to your business rules.