Thank you for contacting us.
' usually occurs when the updated entity is already updated by another context or domain. OpenAccess ORM is trying to updated the record based on its state in current context that might be changed in the meantime. This operations is called optimistic concurrency control. In order to resolve this issue, you should either refresh the context to get the new data or change the behavior of the context to not use optimistic verification if you do not care about this.
Look at this article
to see how you can manage concurrency and this article
to see how to turn off concurrency for a specific entity by using the ConcurrencyMode property.
I hope this information is useful.
Check out the latest announcement
about Telerik Data Access vNext as a powerful framework
able to solve core development problems.