RowVersion platform
Opaque token associated with each record that changes on every modification. Used to detect concurrent update conflicts (HTTP 409).
Detail
In an ERP, concurrent edit conflicts are the norm: two accountants adjusting the same invoice, a batch process running while a user edits. The naive way is last-write-wins, which silently destroys work. The correct way is optimistic concurrency: every GET returns a RowVersion, every PATCH sends it back, and if it changed in between the server responds 409 with the full current entity. cifraHQ Enterprise’s frontend handles enriched 409s: it shows the user which fields changed since their edit and lets them resolve. A small pattern, but it defines the difference between an ERP that loses data and one that does not.
How does cifraHQ model RowVersion?
Let’s schedule a 45-minute technical session with your team to see it in product.