A batched upsert. Unchanged lines are detected and skipped; the remaining rows go in one call, and the order totals are recomputed once. The journey stations reached by the pass are also stamped in one write rather than one round trip each.
Also called: slow save · receiving takes a minute · batch save
- 1Each line is compared against its stored values including notes and photos; identical lines are skipped
- 2upsertItems writes the array natively through the /api/db proxy
- 3recomputeOrderTotals runs once after the batch
- 4recordJourneySteps stamps several stations in one update
'The receiving pass called upsertItem per line, and upsertItem recomputes the order totals — so saving an 80-line order fired 160 round trips and took the better part of a minute. The danger is not the wait: it is that someone navigates away from a spinner they no longer trust and loses the count.' Skipping untouched lines has its own reason: 'rewriting them costs time and tells the audit log a change happened when none did.'
- A minute-long save loses the count when someone navigates away
- An audit log full of changes that never happened
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →