Microsoft have started the Microsoft Dynamics GP 2013 Feature of the Day series on the Inside Microsoft Dynamics GP Blog.
The tenth feature they’ve announced is some enhancements to the Alternative/Modified Forms and Reports window.
This feature covers several enhancements to the window to improve usability.
Continue reading “MDGP 2013 Feature of the Day: Alternative/Modified Forms and Reports”
After installing the Professional Services Tools Library earlier this week, I’m doing a series of posts on the different functions available, for free, within.
This post covers the Copy Shortcuts options. This function allows shortcuts to be copied from on user to another.
Continue reading “How To Copy Shortcuts Using PSTL”
Now that the Professional Service Tools Library (PSTL) has been installed it’s time to take a look at some of the functionality available.
The first one I’ll look at is how to disable a database so users cannot log in. Without using PSTL, to deactivate a database requires you to use the User Access window (
) and select each user in turn and uncheck the company to be disabled. If you have more than a handful of users, this can take a long time to do but with PSTL all users can be disabled very quickly.
Continue reading “How To Disable A Database Using PSTL”
Clients who have upgraded to Microsoft Dynamics GP 2010 can use the new remember user and password functionality, but what about those who have not yet upgraded?
Well, in Microsoft Dynamics GP 10, and before, you can use a login macro to automate the login process. A macro can be created by pressing Alt + F8 on the login screen and following the normal login process before pressing Alt + F8 again to stop recording. Continue reading “Automate Login To Microsoft Dynamics GP 10”
I was working on a client’s system the other day and discovered that no-one knew the dynsa password. Bearing in mind my minor crusade to get clients to stop giving the SQL sa password to the GP administrator, instead giving them the dynsa password, I needed to reset the password.
In theory this should be possible from the User Security window (Microsoft Dynamics GP menu » Tools » Setup » System » User). However. after changing the password I was unable to log into Microsoft Dynamics GP with the dynsa user.
In the end the solution is to remove the password using the SQL Server Management Studio. Next time dynsa logs in the following message will be displayed and force the password to be changed;
Actually, that’s not the question at all; as a general rule of thumb, the sa user should not be used by anyone within Microsoft Dynamics GP. The sa user is the SQL System Administrator user whereas Dynamics GP has it’s own System Administrator user; dynsa.
So, what is the difference between these two system admins? Well, to start with, sa is the SQL Server database administator and, as such, has access too all databases, including non-Dynamics databases, on the SQL Server instance. Instead dynsa should be used as it is the GP database administrator and only has access to the GP databases.
While sa is needed for initial system instllation and configuration, and for some third party add-on administration, it should not be used for day-to-day administration of Dynamics GP. As dynsa is a database owner it can be used for most security and maintenance tasks within GP and, like sa, is granted the Poweruser role automatically.
I have to admit, this is more “do as I say, than as I do” because we have been slightly lax in getting this message out to clients. This is something I fully intend to put right this year as I travel around client sites doing upgrades to Microsoft Dynamics GP 2010; in some cases this may lead to entertaining discussions with various Heads of Finance or Directors of Finance or Resources. However, I think in all cases the clinching argument is that using dynsa instead of sa minimises the possibility of tampering with non-GP databases should the password be accidentally leaked.
Another of the minor new features in Microsoft Dynamics GP 2010 is the ability to copy security from one user to another in the User Security form (Microsoft Dynamics GP menu » Tools » Setup » System » User). Continue reading “Feature Explained: Copy User Security”
I upgraded a customer to Microsoft Dynamics GP 2010 a couple of weeks ago and they have started to explore some of the new features. After fixing their payment run problem they enabled the new functionality for emailing remittances. Continue reading “Not Privileged To Run this Report Error in Payables Select Checks”
Microsoft Dynamics GP does not support Windows Authentication but in Microsoft Dynamics GP 2010 a new option has been added to allow the user’s username and password to be remembered for when they login. This isn’t as good as Windows Auth as the password does not have rules enforced by Active Directory but can make logging in easier for users. Continue reading “Feature Explained: Remember User & Password”