After months of work, I am extremely excited to announce that GP Power Tools for Microsoft Dynamics GP (GPPT) Build 22 is now available for download. Please update your systems to get all the new features.
GP Power Tools was previously known as Support Debugging Tool (SDT), which was discontinued in October 2014. If you are still using the previous product, please upgrade to the supported and much better GP Power Tools product.
A couple of days ago GP Power Tools turned ten years old.
On the 30th August 2006, I decided to create a tool to help identify the cause of a non-reproducible error that was the issue reported in a long running, escalated support case.
This was the first build of the “MBS Support Debugging Tool“.
I am pleased to announce that the next build of GP Power Tools for Microsoft Dynamics GP (GPPT) is now available for download.
GP Power Tools was previously known as Support Debugging Tool (SDT), which was discontinued in October 2014. If you are still using the previous product, please upgrade to the supported and much better GP Power Tools product.
After the huge success at the GPUG Summit 2015 conference, Beat Bucher MVP and I will be presenting an encore performance of our GP Power Tools (GPPT) session as a webinar.
Even though the session title mentions the Support Debugging Tool (SDT), the session focusses on GP Power Tools. This is because the Support Debugging Tool has been discontinued since October 2014 and replaced by GP Power Tools.
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.
Since leaving Microsoft in October last year, I have been asked many times about the future of the Support Debugging Tool.
So I wanted to let people know what is happening with the tool and what to expect.
This is the third and final article in the series, make sure you look at the previous articles before this one.
The previous articles can be found at:
Today’s article adds the final step by adding a method for a user to execute the code we have written so far without requiring access to any Support Debugging Tool windows.
This is the second article in the series, if you haven’t already, please see the previous article: Using the Support Debugging Tool to create user accessible SQL Scripts – Part 1.
Today’s article adds a simple user interface for the previously created SQL scripts using Dexterity sanScript.
It has been a while since I have posted a technical article on the blog. This is because I am spending almost all my time working on bringing some existing and new products to market.
I am still working on the rebranded and improved release of the Support Debugging Tool. There will be a number of improvements in its features and navigation, more on that soon.
For now, I wanted to post a really clever method of using the Support Debugging Tool to provide additional functionality to end users.
Hello to all the fans of the features and functionality offered by the Support Debugging Tool, who disliked the name of the tool.
After consultation with the community, the Microsoft Dynamics GP MVPs (especially Mark Polino, he has always wanted the name changed) as well as polls on this blog, I am pleased to finally announce the new name for the Support Debugging Tool.
As you should have heard by now, Winthrop Development Consultants has an agreement with Microsoft to continue the development and support of the Support Debugging Tool.
It will be re-released once it has been rebranded, renamed and updated.
Following on my previous post: Where is the Support Debugging Tool for Microsoft Dynamics GP 2015? I can now confirm that progress has been made.
Winthrop Development Consultants has negotiated an exclusive agreement with Microsoft to obtain the Support Debugging Tool source code.
Hello everyone
As most of you know I am the developer of the Support Debugging Tool for Microsoft Dynamics GP (SDT).
The SDT has been provided free of charge to Partners and Customers (via their partners) in the Dynamics community since its release in September 2008. The tool and its feature set have come a long way from the public release of build 9 for GP versions 8.0, 9.0 and 10.0.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
IMPORTANT NOTICE: The Support Debugging Tool is now GP Power Tools from Winthrop Development Consultants (http://winthropdc.com/GPPT)
It is time to release a new build of the Support Debugging Tool for Microsoft Dynamics GP for versions 10.0, GP 2010 (v11.0) and GP 2013 (v12.0).
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
This post revisits the issue previously discussed in the blog post:
Continue reading
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
A while ago I had a case where the customer was storing data in the DUOS (Dynamic User Object Store) table from a VBA (Visual Basic for Applications) customisation. Everything worked fine until the users switched companies. After switching company the VBA customisation would still be connected to the DUOS table in the previous company’s database. If the user exited Microsoft Dynamics GP and logged back in, the DUOS in the correct database was used.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
GP Power Tools – Administrator Tools Module can provide this functionality without needing customizations. (http://WinthropDC.com/GPPT)
Recently a comment from David M (not me) was posted on the Support Debugging Tool Portal page asking:
“We have some fairly long names for our GP companies. Well, when logging onto GP, the second “Company Login” screen cuts off the company names too short for us. The entry field for companies allow for longer strings (65 Characters) but only displays 31 characters on the pull-down list. There is plenty of real estate on this window going unused. Can anyone think of a way to enhance/fix this to display more of the company name?”
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
IMPORTANT NOTICE: The Support Debugging Tool is now GP Power Tools from Winthrop Development Consultants (http://winthropdc.com/GPPT)
This is a reposting of an article Tracy Steere originally wrote on my Developing for Dynamics GP blog.
Hi, my name is Tracy Steere and I work with David Musgrave on the Microsoft Dynamics GP Asia Pacific support team.
Winthrop Development Consultants Blog 