We are experiencing an issue in Business Central Cloud where the system displays the error message:
“We can’t save your changes right now because a record in table ‘…’ is being updated in a transaction done by another session. You’ll have to wait until the other transaction has completed, which may take a while. Please try again later.”
This occurs when trying to post different documents at the same time but also during the process of closing a transaction on the POS in our stores, resulting in record locks that prevent transactions from being completed.
We use LS Central Extension for retail.
That error is the absolute worst! It’s a classic database locking problem common when high-volume systems like LS Central push rapid transactions into Business Central Cloud. It’s essentially a database traffic jam.
We’ve seen and fixed this exact issue for a client in the manufacturing industry who was generating massive transaction volumes quickly. If it worked for them, it might be the simple tune-up you need too!
Your Partner Must Audit These Three Areas:
Number Series Bottlenecks: Is every POS lane sharing the exact same Number Series for documents? This becomes the single point of failure and causes widespread locks. Separating Number Series often fixes lock issues immediately.
LS Central Transaction Timing: The partner needs to audit the LS Central code that runs when you “Close a Transaction.” If that code holds onto a record lock for even a fraction of a second too long, it causes the jam. Optimization here is critical.
Posting Groups: Check if overly consolidated Posting Groups are forcing too many transactions to hit the same handful of records, which increases the lock risk.
Next Step: Let’s Share Insights
The fix is a technical tune-up of your BC/LS configurations to reduce that transaction traffic. If you’d like to share insights on your specific setup, we can arrange a free 30-minute audit session. We can quickly review your configuration and confirm what the exact solution should be.
You need to use specialised Performance Logging and Monitoring Tool for Business Central and Dynamics NAV to get to the bottom of this issue. On the surface it may look like an issue with LS Central function / extension, but until you use tools like SQL Mantra Tools Performance insights (see SQL Mantra Tools - The Performance Tuning Experts for Business Central ) you will not see the full story of what is calling what and hence identify the source of the issue with pin point accuracy. Their tools interface is very easy to use and you can diagnose the problem your self. You any need some of their expertise to fix the issues. They have a lot of experience working with LS central in the past. Best advise is to contact them see SQL Mantra Tools - The Performance Tuning Experts for Business Central . Hope this will help. No point wasting our time speculating about the source of the performance problem without the help from experts like SQL Mantra Tools.