It could happen that the messages “another user has modified” or “a table is locked by another user” appear, in this case you have to wait for the situation to be unlocked, by letting the users out or waiting.
Currently the only way to break the deadlocks
- wait and wait…
- get all users out, check that the situation has been unlocked
try to enter data with another user in the same tables.. do something in tables to unlock….
.. finally ask Microsoft to reset the instance (at night) by opening a ticket.
Surely they will be working on a better management of the sessions through telemetry or other .. I don’t know. To date, the only solution that came to my mind is to do the old way, that is, to install a session killer in BC SaaS.
In practice it is possible to see the active sessions but it is not possible to delete them, to do this it is necessary to install the usual page that takes care of killing the active sessions.
*** DISCLAIMER ***
“Obviously it is not recommended to use it! it has been tested in a sandbox but also works in a production environment.”
The “Active Sessions” Table
You can open Sessions and Active Sessions tables
…but you can only see the list of All open sessions, nothing more as the table is read-only (a SQL view) in read only state by Design).
The “KILL ACTIVE SESSION” Page
With this simple sample Page (Kill Active Session), you can filter and delete the selected Session.
Install the extension
Download Link on GitHub
#1 – Search for “Active Session” page
#2 – Filter the needs session
#3 – Select the line and run “Delete Line”
#4 – The system show the Confirmation Message “Go ahead and delete ?”
.. and immediately…. The Session if Killed!
… and after some second… the user is disconnected from the browser because the session has been killed!
YOUR SESSIONS IS EXPIRED! ….