Skip to main content

Notifications

Community site session details

Community site session details

Session Id :

Microsoft Dynamics GP 2016 R2: Show user name in message when it is edited by another user

Terry R Heley Profile Picture Terry R Heley Microsoft Employee

Hello Everyone,
In Microsoft Dynamics 2016 R2, users will now receive a detailed message displaying the User that is currently modifying a Batch when they are trying to delete or post a batch is when this error typically appears.
In the below example, user Steve is attempting to modify a GL Batch that is already opened by user Bill.  Steve receives the following message:

      8547.BatchEntry.PNG7080.user.PNG

So users no longer need to reach out to their colleagues to find out who has a hold on editing the batch.

Click HERE for more detailed documentation for Dynamics GP 2016 R2 features.
Dynamics GP 2016 R2 feature VIDEO click HERE!

Be sure to check back to the Microsoft Dynamics GP 2016 R2 Feature Blog Series Schedule page to review posted blog articles and upcoming blog posts to help you gear up for What's New in Microsoft Dynamics GP 2016 R2 with great content, documentation, and videos.

Thank you,

Jeff Zens | SR Support Engineer| Microsoft Dynamics GP

Comments

*This post is locked for comments

  • Lisa Williams Profile Picture Lisa Williams 99
    Posted at

    Jeff & Terry - A client that just upgraded to GP 2018 R2 said the name isn't listed in the "This transaction is being edited by another user." message when they select a Sales Order in Sales Order Fulfillment.  My guess is that this functionality was added in most places within the GP code, but not all?  Can anyone at Microsoft confirm this for us?

    Thanks,

    Lisa Williams, Velosio

  • mikepeck Profile Picture mikepeck 356
    Posted at

    I have a user who is receiving that message, and the user is ....himself! I had him log out, I cleaned up all activity records associated with his user ID, Checked SY0500, the batch record was showing Marked to Post and Batch Status both-0-. When the user logged back in, he continues to receive the message. Has anyone else encountered this? How did you go about clearing the message. (The Batch is Unapproved when I check it as 'sa').