"We can't save your changes right now, because a record is being updated in a transaction done by another session."
Very likely every Business Central developer who has been in the field for a while, had to debug this error at some point in their professional journey (and probably you did not enjoy it).
What could cause this error and how to make sure that users see it as rarely as possible (preferably never)?
In my session I'm going to delve into some aspects of application development that impact concurrency. I will talk about session contention and concurrency and discuss coding practices and application design approaches which can help to reduce the number of update conflicts and ensure maximum transaction throughput.
What are the most typical sources of conflicts, how to avoid them, and what are the risks and trade-offs to keep in mind - these are the questions I will try to answer in this session.
Speaker(s)