Rather than just leaving the Microsoft Dynamics GP Book Roundup as a post, I have made it a page available from the GP Resources menu.
I will be doing my best to keep this page up to date; if I have missed any books on Microsoft Dynamics GP, please get in touch and let me know so I can add the book.
I accidentally missed the Dynamics GP 2016 Security and Field Audit book by Mark Polino and Andy Snook from the round up post, but have added it to the page.
The new GP books resource page is here.
There are a number of books available for Microsoft Dynamics GP which have been written by various people across a umber of years (although a few names crop up repeatedly). I thought it might be useful to list the books which are currently available for each version of Microsoft Dynamics GP; some of the books are only available for older versions of Dynamics GP, but the information within is still mostly relevant.
To avoid any appearence of favouritism, I have listed them in Dynamics GP version and author surname order (when multiple authors, the first listed author’s name is used).
Where there is no version in the name I have made by best guess as to which version it was written against.
Microsoft Dynamics GP 2018
Microsoft Dynamics GP 2016
Continue reading “Microsoft Dynamics GP Book Roundup”
I’ve been working with a client recently on an upgrade to Microsoft Dynamics GP 2018 and all has gone well overall. However, they had a security project running at the same time, where they were changing the passwords for a number of accounts including the SQL Srver sa account.
Unfortunately, the password length they were setting was 20 characters,. They supplied the new password to me, but I found I couldn’t log in. When I then tried to copy and paste the password into the field, nothing happened (which is what clued me into the issue).
The cause of this login issue, is that the Password field on the Users Master (SY01400) table has a maximum Keyable Length of 15 characters, and this restriction is enforced on all user ids entered on the login window.
So for me to complete the final steps of the upgrade, the password for the sa account was changed to a 15 character one; after the upgrade was complete, the password was again changed to a longer one and then the account disabled.
Best practice is to use the sa account to administer only SQL Server and to use either a named user account in Dynamics GP or to use the DYNSA account. I am encouraging all clients to ensure this is the case.
There is a wide range of ways you can better secure your system. One way of working through these is to engage with your partner and another is to purchase the Microsoft Dynamics GP Security and Audit Field Manual: Dynamics GP 2016 book by MVP Mark Polino and Andy Snook. This book is for the 2016 version of Dynamics GP, but still fully applies to Microsoft Dynamics GP 2018 (as well as earlier versions).