Back in August 2006, while at Microsoft, I started development on a Dexterity based tool designed to use programmatic control Dexterity logging and table based triggers to capture three logs leading up to a non reproducible data error occurring in the tables. This was build 1 of the MBS Support Debugging Tool.
In September 2008, the renamed Support Debugging Tool (SDT) build 9 was released to the GP partner and customer community for them to use and help support their Microsoft Dynamics GP systems. For the next 6 years, I continued to work on the SDT pet project (builds 10 to 19) in my own time as it was not officially part of my role at Microsoft.
When my team was shut down and my role discontinued in October 2014, I left Microsoft and lobbied to get access to my code. Thanks to the support and efforts of Pam Misialek, I was able to get the license the code, which was rebranded, renamed and re-released as GP Power Tools build 20 in August 2015.
Ever since the start of this project in 2006, the functionality and features of the tool (regardless of name) has been based on feedback and requests from the community. Understanding the issues and pain points faced by users and administrators has shaped the development of the tool.
While I get to hear when there are issues or when additional functionality or features are wanted, I rarely get to hear how GP Power Tools has solved your pain points and made your lives better. So I was delighted to see a thread on the GPUG Open Forum discussing the experience of users of the product:
Please feel free to share your experiences with GP Power Tools on this thread and spread the word about the benefits it provides at a very reasonable cost.
Thanks for sharing.
PS: Adding the forum feedback as comments on this post.
This article was originally posted on http://www.winthropdc.com/blog.