Avery.Software — Native Execution Runtime
RuntimeUse casesPricingHelpBlog
← Back to helprecipe · apps

Resolve a spreadsheet drift / sync conflict

2 min · 4 steps

When the .xlsx + the app both changed, the Sync tab's diff viewer shows you every conflicting row.

Drift happens when both the workbook and the app changed since the last sync. The Database → Sync tab's diff viewer surfaces the per-row, per-cell delta with severity styling (additions in green, deletions in red, modifications in amber).

Steps

  1. Open the Database tab → Sync sub-tab.

    Inside the project workspace.

  2. Click 'Diff' to fetch the latest workbook delta.

    Avery reads the file, computes the diff, and renders the conflict report. Each row shows: was-in-app, was-in-file, current-in-file. Cells that match are folded.

  3. Pick a conflict policy.

    Three options: • Overwrite app — the file wins. App rows changed since the last sync are LOST. Pick when the file is your source of truth (finance ledger, ops sheet). • Keep app — the file's changes are ignored on this pull. The next push will overwrite the file. Pick when you trust the app's state. • Per-row prompt — you decide each conflict individually. Slower but safe; pick when changes are mixed.

  4. Apply.

    Avery runs the chosen policy + writes a row to `.nxr/audit.json` recording every applied change. If anything goes wrong (file locked, exceljs parse error), the app's state is unchanged + the error surfaces in the banner.


Live recipes need the desktop

This article is a static preview. The in-app Help sidecar inside Avery NXR can fire each step against your live project — install the desktop to use it interactively.

Download desktop →