A concurrency violation essentially means that the row in the database could not be added. In the case of saving a record, this refers to the fact that the information contained in the record could not be added to one of more of the database tables that are supposed to receive the information.
It is quite rare to see this error, as this requires two process to affect the same database table, at the same time. As each record is added to the software, it is allocated the next sequential primary number. If someone else tries to create a new record at the same time as another user deletes the previous record (for example) then you may see a concurrency violation at this point.
A concurrency error can also be shown if another user has updated a record while the same record was open on another users screen.
In most cases, if the user logs out of the software and re-enters the record, this will then save as expected. However, if users are seeing concurrency errors on a regular basis, please raise a case and reference the title of this article.
Concurrency violation - error shown when saving record
Updated over a month ago