Hi Florian,
Yes, this is a known bug.
You can work around the issue by getting the inner exceptions of the OptimisticVerificationException.
The Refresh call will update the in-memory object with latest values from the database.
Do get back in case you need further assistance.
Regards,
Ady
Telerik
Yes, this is a known bug.
You can work around the issue by getting the inner exceptions of the OptimisticVerificationException.
01.catch(Telerik.OpenAccess.Exceptions.OptimisticVerificationException ex)02.{03. var optimisticVerificationExceptions = ex.InnerExceptions.Where(x => x.GetType() == typeof(OptimisticVerificationException));04. foreach(var innerEx in optimisticVerificationExceptions) 05. {06. var failedObjectId = innerEx.FailedObject;07. context.Refresh(Telerik.OpenAccess.RefreshMode.OverwriteChangesFromStore, failedObjectId)08. } 09.}The Refresh call will update the in-memory object with latest values from the database.
Do get back in case you need further assistance.
Regards,
Ady
Telerik
Check out the latest announcement about Telerik Data Access vNext as a powerful framework able to solve core development problems.
