Click here to
Subscribe to
our Newsletter
Recently, I read a couple of articles by my fellow bloggers in the Microsoft Dynamics GP community and wanted to highlight them as well as add some of my own thoughts.
The first article was from Tim Wappat at Dynamic Code Blocks. It was a summary of the sneak peak at Microsoft Dynamics GP 2016 and its HTML 5 web client at a meeting in London, UK.
Today, I am proud to announce the upcoming release of a new product from Winthrop Development Consultants.
Welcome to Batch Posting Service Toolkit for Microsoft Dynamics GP for versions GP 2010 (v11.0), GP 2013 (v12.0 including R2) and GP 2015 (v14.00 including R2).
If you come across the problem below, please download the GP Power Tools Build 20 hotfix 2 which is now available from the Mekorma website.
When using the Configuration Export/Import window to import a configuration settings file created with the Support Debugging Tool into GP Power Tools, it will say that there is nothing to import.
This issue was caused by the changes to make GP Power Tools work with SQL tables rather than with temporary tables written to a Debugger.xml file. It happened because the table names written into the configurations settings file was incorrectly changed so that they had a _TEMP suffix.
This blog article has been prompted by the thread below on the Microsoft Dynamics GP community forum:
I had responded with some information on the thread, but when I tried to implement the suggestions I made, I found that it was not actually possible and that other methods would be needed.
If you follow this blog, I am sure you already know that GP Power Tools has been released through my distribution and support partner, Mekorma, for Microsoft Dynamics GP 2010, GP 2013 and GP 2015.
The question I am hearing now from existing Support Debugging Tool sites is:
“Now that GP Power Tools is available, what happens to my Support Debugging Tool installation?“.
Now that GP Power Tools has been out for a little while and I have recently released a hotfix that improves the installer as well as fixes some issues found with the tool, it is time to explain how the installer works and answer some frequently asked questions.
Please note that some of the information in this article only relates to the build 20 hotfix (Last Modified: 19-Aug-2015) or later. If you are unsure what build you have, just go and download the latest installer from the Winthrop website. If you look at the installer’s properties, the File Version will show as XX.0.20.4 or later.
I know that I should not be surprised as I have been in this industry for so long, but after all the work and testing done prior to releasing GP Power Tools Build 20, we have still come across some issues that needed fixing.
You probably won’t come across most of the issues as they relate to problems caused when company databases are not installed or are offline for some reason. Anyhow, GP Power Tools is now smart enough to handle these extra situations.
Over the past few weeks I have been posting a number of “What’s New” articles for GP Power Tools build 20.
If you have missed any of them, this article has all the links to the articles, so you can read them at your leisure.
GP Power Tools is the first product that I have released over the years to have a proper installation program. As the complexity of the products increases and there are more files involved than a single Dexterity chunk (.cnk) file, it became necessary to use an installer rather than just a zipped archive file.
GP Power Tools has a number of DLL files as well as a text file with version history, a license document and the user guide PDF.
Microsoft Dynamics GP 2015 added Service Based Architecture (SBA) and .Net Interop functionality to the application. Service Based Architecture allows the Dexterity developer to write global procedures and use meta data to expose these service enabled procedures to the outside world as REST Web Services.
GP Power Tools provides five Service Enabled Procedures which can be used to execute custom business logic created in the Runtime Execute window. These services can be called as Web Services, from Visual Studio Tools using Visual C# or Visual Basic.Net, or from any Dexterity product dictionary using sanScript.