With year-end procedures in full gear, Microsoft has released Dynamics GP 2016 R2, the latest in the Dynamics GP series. This year, they’ve done something a little bit different by combining the year-end update for GP 2016 with the R2 service pack, meaning that if you're using GP 2016, they are one and the same download. This is convenient, as it helps minimize the level of effort needed to make sure the system stays current into the new year.
As per the usual practice, Terry Heley has come out with a blog post highlighting the new features included in GP 2016 R2. The post by Terry links to an in-depth article on each of the new features and each article is written by a member of the GP Dev/Support team. Below, I've summarized a few of the most pertinent features, which will likely appeal to a wide audience of GP users:
Smartlist Favorite Protection
I think most users who are familiar with Smartlist have probably been there at one point or another. You have a Smartlist which you frequently use to check up on the amounts in the system, and you've painstakingly crafted this Smartlist by adding just the columns you need, removing the extraneous, until it has become a thing of beauty. Then, Joe from down the hall has to go in and check something, and the next thing you know, the Smartlist has been mutilated beyond recognition.
With this new feature, you can set the security for a given Smartlist so that it is now protected from anyone who doesn't have the password. When a user attempts to modify an existing Favorite, they will receive a warning to the effect that they are going to change the current Favorite. Anyone who does not have the password will not be able to change the Smartlist.
Here is the link to the full post with screenshots:
https://community.dynamics.com/gp/b/dynamicsgp/archive/2016/12/08/smartlist-favorite-protection"This batch is being edited by another user" now shows name of user editing batch
Another very handy feature. Many users have been in the position where they are trying to finalize and post a batch, only to receive an error upon accessing the batch that "This batch is being edited by another user." With this new functionality, GP queries the batch activity table (SY00800) to determine which user has a hold on the batch. This means that users no longer have to go hunting up and down the halls (or the phone extension list) to find out who is editing their batch. Instead, they will receive a message similar to the following:
"This batch is being edited by Andrew. Please try later."
The users can now go directly to the person in question to find out why this is happening. As a pro-tip, if you receive this error and your username is the one being referenced, make sure you have all other transaction/batch entry windows closed.
Here is the full link with screenshots:
https://community.dynamics.com/gp/b/dynamicsgp/archive/2016/12/13/microsoft-dynamics-gp-2016-r2-show-user-name-in-message-when-it-is-edited-by-another-userPayables Management credit card invoices now link to original invoices
Credit cards have always been a bit tricky to handle in ERP software. If you use credit cards in payables management in GP, you know that creating a credit card payment also creates an invoice to the credit card vendor. This is to account for the fact that you owe the credit card company the money paid to the original vendor. Before GP 2016 R2, there was no visible link between these invoices, which made it difficult to tic-and-tie transactions without reviewing potentially several transactions.
With GP 2016 R2, when you create a credit card payment, the invoice is still automatically created, but it now contains a reference to the original invoice in the Transaction Description field, visible from any of the Payables Inquiry windows. Also, this also changes the way that the GL Reconcile tool handles these invoices. Where a credit card invoice would previously appear under Unmatched Transactions, in this version you will see the offsetting transactions from the original invoice and related credit card payment. This will likely save an untold number of headaches from spending late nights trying to trace unmatched transactions on the GL Reconcile report that are simply credit card transactions.
Finally, there is training material available that covers the full list of new functionality in GP 2016 R2. I've linked to it on this blog - if you have any questions on these features or anything else in your GP implementation, please don't hesitate to reach out to us at firstname.lastname@example.org.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.