EasyDigz watches the MLS for changes to properties in your database and applies them. The interesting part is what it does when you have also edited the same field.
#The rule
| Situation | What happens |
|---|---|
| MLS changes a field you have not touched | Applied automatically. Nothing to do |
| MLS changes a field you have edited | Flagged as a conflict. Neither value is lost, you decide |
Your work is never silently overwritten
This is the whole design. You get MLS accuracy without losing local knowledge you added by hand.
#What updates on its own
Price changes, status updates, showing instructions and description changes, the things that move often and that you rarely override.
#Three examples
| Scenario | Result |
|---|---|
| MLS moves a property from Active to Pending, and you never edited status | Updated automatically |
| You added local school detail the MLS does not carry, and the MLS updates other fields | Your school detail is untouched |
| You corrected the square footage from a survey, and the MLS later changes the same field | Flagged as a conflict for you to resolve |
#When there is a conflict
You are notified and can review each one side by side. See Resolving sync conflicts.
#Why this matters
Without it you choose between a database that goes stale and one that erases your corrections every night. The conflict step is the small price for having neither.