A conflict means you edited a field and the MLS later changed the same field. Rather than pick a winner, EasyDigz stops and asks.
#Resolving them
- 1
Open the conflicts screen from the notification.
- 2
Compare the two values side by side.
Your local value and the incoming MLS value.
- 3
Choose.
Accept the MLS value, or keep yours.
- 4
Work through them individually or in a batch.
Batch is fine for a set that all have the same answer.
#What each choice does
| Choice | Now | In future |
|---|---|---|
| Accept the MLS value | Your edit is replaced | That field syncs normally again |
| Keep yours | Your value stays | That field stops auto-updating, it is protected from then on |
Rejecting an MLS value marks that field as yours. It will no longer update automatically, so if the MLS later becomes the better source you will not be told. Use it for things you genuinely know better, a corrected square footage from a survey, not to win a one-off disagreement.
#Which to choose
| Choose the MLS value when | Keep yours when |
|---|---|
| It is a fact the MLS owns, price, status, dates | You corrected an error and have evidence |
| You edited it casually and do not care | You added local knowledge the MLS does not carry |
| You are not sure | You are certain |
Resolutions are recorded, so you can see later what was changed and why.
#If conflicts keep appearing on one field
Repeated conflicts on the same field usually mean the MLS record itself is wrong. Fixing it at the MLS is the durable answer, otherwise you are re-resolving the same disagreement indefinitely.