Click here to
Subscribe to
our Newsletter
I am so proud and excited to finally release the much anticipated replacement for the discontinued Support Debugging Tool.
Welcome to GP Power Tools for Microsoft Dynamics GP for versions GP 2010 (v11.0), GP 2013 (v12.0 including R2) and GP 2015 (v14.00 including R2).
This first release of GP Power Tools will be build 20 and includes many new features, enhancements to existing features as well as rebranding as a Winthrop Development Consultants product.
One request that I have heard a number of times is for a method to expose scripts written using Runtime Execute or SQL Execute to normal users.
Because these windows are Advanced Mode features designed for administrators to use, they require SQL Server sysadmin or dbo privileges as well as application level security and the System password (if used) to access.
The Support Debugging Tool already has the ability to create and execute Dexterity sanScript and Transact-SQL scripts, without needing the Dexterity development environment or SQL Server Management Studio installed.
Now GP Power Tools adds the ability to create and execute Visual C# scripts and Visual Basic.Net scripts, without needing Visual Studio installed.
The Administrator level (Advanced Mode) features of GP Power Tools require application level security, SQL Server sysadmin or dbo status and the System Password (if one is configured) to access them.
So what happens if you want a user to be able access a feature and can provide the security required at the application level and SQL Server level, but you don’t really want to provide them with the Microsoft Dynamics GP System password?
As GP Power Tools approaches release, it is time to continue the What’s New series and explain another of the new features added to the product.
You can now enable Security Activity Tracking to collect statistical data on the usage of the various resources and security objects within the system.
Today, I was contacted by a fellow Dexterity developer who was having trouble getting Dexterity for Microsoft Dynamics GP 2015 or later to run Dynamics.dic in Test Mode.
In this article, I will take you through the errors you could get and how to resolve them. Some of these you might know from previous versions, others are new to GP 2015 or later.
Part of the #Dexterity Development Environments Series. See Summary at end for quick list.
As mentioned in recent posts, GP Power Tools is almost ready for release. The user guide manual documentation is now completed… all 256 pages of it. If you want to get the code now, you can already install the public beta and upgrade to the final release later.
This is the first article in a series of What’s New posts for GP Power Tools. The aim of this series is to highlight some of the new features of the tool and flesh out more details than the 21 reasons to upgrade article.
As the release of GP Power Tools approaches, I am hearing the following question from existing users of the Support Debugging Tool:
“Why should I pay to upgrade to GP Power Tools when the Support Debugging Tool is free?”
Today, I am releasing an update to the GP Power Tools Public Beta.
If you have installed a previous version, please download and install this updated code as it contains a number of cosmetic and performance changes that have been identified by beta testers and during the documentation process.
Now that the GP Power Tools Public Beta is out there, I know that people will not read the user guide documentation (GPPTools.pdf).
So I thought it would be worth while mentioning some guidelines to make the install as smooth as possible.