Click here to
Subscribe to
our Newsletter
You might have seen some postings on Twitter, Facebook and LinkedIn mentioning that I have been working hard on the next release of GP Power Tools. Well, all the major features planned for Build 27 have been completed.
All that is left to do is beta testing, documentation and a couple of minor features and then it can be released to the Microsoft Dynamics GP community in time for the upcoming conference season for 2019.
A while back I had a customer site reporting an issue where a small window would open every time a user opens the Sales Transaction Entry (SOP_Entry) window.
This issue only occurs when the GP Power Tools – Administrator Tools module feature to prevent windows opening outside of the visible display is enabled.
A recent support case identified that, on systems which are not internet connected, Winthrop Development Consultants products can cause a significant delay when logging into Microsoft Dynamics GP.
This article explains the cause and what has been done to resolve this issue in the latest builds.
With the release of GP Power Tools build 26 yesterday, Microsoft Dynamics GP System Administrators now have a new tool for managing their User Licenses.
GP Power Tools build 26 adds a suite of new features specifically designed to help administrators track, analyze and control how their user licenses in Dynamics GP are used.
Yesterday GP Power Tools build 26 was released. This build has numerous enhancements to existing functionality as well as some awesome new features. Automatic Logout has been enhanced further in builds 27 through to build 29.
One of the features that has been requested by the community for a while and is now included in the GP Power Tools – Administrator Tools module is Automatic Logout.
The best thing is that all existing GP Power Tools sites get all the new features for free just by updating their system to the current build. Download from here.
Winthrop Development Consultants is pleased to announce Build 26 of GP Power Tools (GPPT) for Microsoft Dynamics GP was released on 12-Feb-2019.
This build incorporates many new features and enhancements to all modules of GP Power Tools. It also includes a number of code improvements and fixes to improve existing functionality.
As mentioned in my previous post I have been working hard for the last few months on the development of the next build of GP Power Tools.
Build 26 of GP Power Tools is already at release candidate stage and I am just working on getting the documentation for the User Guide manual updated and tweaking any issues found during beta testing.
Every now and then a support request comes in where a customer has received an error message referencing the ‘MBS_ScreenShot_Forms’ table. These support requests are usually redirected from Microsoft’s support team. The error is caused by environmental issues and are generated from GP Power Tools (or its predecessor, the Support Debugging Tool).
This article explains what can cause the error and provides suggestions on how to modify your environment to avoid the issue re-ocurring.
Selling GP Power Tools for Microsoft Dynamics GP has always been an interesting affair. If you can get a customer to sit and watch a demo (live or on video from the GPPT Portal), they immediately see the benefits and want the product. However, it is usually the people who work with the product day to day who see the demo and then they find it hard to sell to management.
You might have seen my posts on Twitter and Facebook recently about my new toy mini laptop PC, the crowd funded GPD Pocket 2.
I have been burnt before with crowd funded projects (I supported 3 smartwatches and only one make it to production and it under-delivered 🙁 ), so I was wary of getting involved again. However, this was the second generation of the GPD Pocket and demo devices had already been delivered to a number of YouTube reviewers. I felt fairly safe to get involved with crowd funding again, as this would give me a discount and get the device earlier.