Initially, I published a script that would return a list of SOP Documents with the User ID that had a lock on each:
Then, a client with a large number of order processing users requested that I use that script to display which user has a document locked when presented with the standard "This transaction is being edited by another user." message in Sales Order Processing when attempting to access a document that is... well... being edited by another user. I did that with VBA and recently decided that would be better produced with Visual Studio Tools as a .dll that you could drop into your Addins directory instead of having to deal with edits to VBA projects. Some details of that initial release were documented in this blog post:
http://mbsguru.blogspot.com/2011/02/record-lock-trace-addon-for-dynamics-gp.html
Since, I have extended it to replace the same "This transaction is being edited by another user." message in Purchase Order Entry with a message that will specifically identify which user has the Purchase Order locked. I have other plans for this utility and will post updates as I add those in.
Below are the release notes to date:
02/13/2011 - Replace "This transaction is being edited by another user." in SOP with a message that will specifically identify which user has the Sales Document locked.
02/16/2011 - Replace "This transaction is being edited by another user." in POP with a message that will specifically identify which user has the Purchase Order Document locked.
(v2) 08/28/2011 - Replace "This batch is being edited by another user." in SOP with a message that will specifically identify which user has the Sales Batch locked. http://mbsguru.blogspot.com/2011/08/record-lock-trace-v-20.html
(v2) 08/28/2011 - Clear all records that are locked by users that are not actively logged in to GP. http://mbsguru.blogspot.com/2011/08/record-lock-trace-v-20.html
More to come...
Download Record Lock Trace for Dynamics GP
