This page will automatically update as new series are created; the index is in reverse order with newer series at the top.
A fresh install of Dynamics GP includes all of this new functionality by default, but an existing implementation is not updated.
The reason it isn’t automatically updated is to allow the client to decide if the new functionality should be updated or not. To facilitate this, the Dynamics GP Support and Services Blog provides a script for each version with SQL insert statements for the new roles and tasks.
I’ve previously had a post which I updated with this information, but have now created a permanent page linking to the scripts.
I’ll be keeping this page updated in future for all new versions.
The seventeenth Feature of the Day is new totals print on the Payroll Check Register report for FICA.
This feature adds totals to the print of the Payroll Check Register report for FICA. A new Total FICA Owed, Total Employee FICA owed, and totals for both FICA Medicare and FICA Social Security all print on the payroll check register report:
The sixteenth Feature of the Day is shared maximum benefit and deduction code in Payroll..
Thsi feature is a shared maximum benefit and deduction code in Payroll. A new Ded/Ben Shared Limit Setup window allows you to setup a calendar year maximum for multiple benefit and deduction codes. When the check run is processed, it will look at the year-to-date amount and compare it to the calendar year max in this new window.
The fifteenth Feature of the Day is a new Start Date and End Date for each pay code.
This feature adds a new Start Date and End Date for each pay code in the Employee Pay Code Maintenance window. This is used when building the check run as to whether to include the selected pay codes; so if the check run is before the start date or after the end date, that pay code will not be included.
The fourteenth Feature of the Day is Duplicate Check Numbers option extended.
This feature sees the Checkbook Maintenance () option to allow or not allow Duplicate Check Numbers extended to other windows. This means that if this option is not marked, duplicate checks are not allowed in these three windows. Previously, this option only applied to Payables checkbooks but now it includes:
- Bank Transaction Entry
- Payroll Manual Checks
- Miscellaneous Checks
I don’t recall this ever coming up before, so I actually thought the Bank Transaction Entry and Miscellaneous Checks window already did this. That said, we don’t have that many clients using the standard Bank Rec window and none would use the Miscellaneous Checks window as virtually all payments in the UK are via EFT.
The thirteenth Feature of the Day is Email Customer Statements.
This Feature of the Day is all about convenience of sending customer statements. In Dynamics GP 2018 R2 users can email customer statements directly from a button on the action pane in the Customer Maintenance window (
This feature builds on the Single Customer Statement new feature from Dynamics GP 2018 RTM; the original feature of the day post from Microsoft said “print”, but the linked PowerPoint dsaid “email”.
I believed the email part and when I got hands on with the feature was disappointed to find it was only a print.
I’m assuming this feature for 2018 R2 is in response to my, and others, feedback on the print option. I’m very happy to see this has been expanded to an email option now as this will make this feature usable to quite a few of my clients.
The twelfth Feature of the Day is a password expiration notification.
This feature is a new notification reminding you that your password will expire in 7 days and prompting you to change it:
I’d be a lot happier if the number of days is configurable as a reminder and reset prompt starting 7 days before expiry is too early a reminder. I have a few clients who have a password policy of the password expiring and needing to be reset every 30 days.
All a prompt 7 days before does is encourage users to change their password when first prompted; this means they change their passwords every three weeks. This massively contributes to password fatigue, leading to the users writing down their password on a post-it note as they don’t, or won’t, remember the password.
A very laudable addition, much beloved by people who write password policies, but, in my experience, the reality on the ground is that this type of policy and early reminder causes more problems than it solves.
Perhaps people would like to share their experience/perspective below? (Due to massive amounts of spam, comments need to be approved before they appear).
The eleventh Feature of the Day is increase Dynamics GP password maximum length.
This feature see the maximum length of the password usable with Dynamics GP increased from 15 to 21 characters.
Microsoft say that the length of the password in SQL is 21 and this has been matched that so now the maximum password length is the same for Dynamics GP.
I’m not sure where in SQL the length is 21, as in Dynamics GP 2018 RTM, the password length on Users Master (SY01400) is 15 keyable characters; SQL Server supports password lengths of 128 characters.
While 21 characters is an improvement over 15, it would have been nice to see even longer passwords supported.
The tenth Feature of the Day is exclude items on HITB report with zero quantity or value
The Historical Inventory Trial Balance (HITB) report has two new options for Dynamics GP 2018 R2; when printing the HITB report you can now decide if you want to include/exclude items with a zero quantity or value. The new options are:
- Include Items with Zero Quantity
- Include Items with Zero Value
These items will be excluded on the report if the options are not checked; previously, by default, these items were included. Make sure the checkboxes are unmakred to exclude the items with either zero value or quantity:
This is a good update to the HITB; I have a number of clients with large number of items which will generally have a zero quantity of stock while having other items with stock levels they on which they would want to report. Being able to exclude these will make the report usable.