Form versions
If someone else (or the office) updated the form while your answers were still local, Field does not overwrite the server automatically.
Screen path: form row or Sync → Needs attention. You may see This form changed on the server with Server vs This device and Correct and resubmit. Native Field is not the Field PWA.
Preconditions
Section titled “Preconditions”A submitted or in-progress form whose server instance moved. This is an uncommon recovery path, not an everyday two-writer workflow. Per-technician forms do not invent a merge UI.
- Read the notice. Your answers stay on the device; the server is not overwritten automatically.
- Compare Server vs This device.
- Use Correct and resubmit only after you have read the row.
- Open Sync → Sync now. Do not tap Submit form again to force a second write.
- If the checklist still looks wrong, stop and ask the office.
Sync may also list Someone else updated this item. Review and resubmit.
This is not a polished two-writer merge studio. There is no fake conflict screenshot in this documentation. Follow the notice, then Sync now.
What works / does not work
Section titled “What works / does not work”| Works | Does not work | |
|---|---|---|
| Keep local answers on device | Yes | Automatic overwrite of the server |
| Correct and resubmit after review | Yes | Generic “Keep mine / overwrite server” |
| Everyday shared-checklist collision | Not guaranteed | Inventing a FIELD-013 merge studio |
If Needs attention is not a form change: read the Sync row first. Not every attention row is a version collision.
Related: Server authority · Conflicts.