Optimistic concurrency with rowversion — how to handle multiple API calls before Save?
I have a form that loads multiple records and reads the table rowversion. While the user is still on the form, they can call other APIs (add attachment, add certificate, etc.) that internally update the same record and therefore change its rowversion.
When the user finally hits Save and sends the original rowversion, the server rejects it with a concurrency conflict even though no other user touched the record.
What is the correct pattern to handle this? Is it normal to return the updated rowversion after every intermediate API call and have the client track it, or is there a better approach?
Thanks