This is the fourth article in the series on making window fields required. If you have not yet read the introduction article to the series, please read that first:
This example uses GP Power Tools code to make the Substitute Item 1 field on the Item Maintenance Options sub window (same form) required.
This is the third article in the series on making window fields required. If you have not yet read the introduction article to the series, please read that first:
This example uses GP Power Tools code to make the Tax Registration Number field on the Vendor Maintenance Options sub window (same form) required.
This is the second article in the series on making window fields required. If you have not yet read the introduction article to the series, please read that first:
This example uses GP Power Tools code to make the Tax Registration Number field on the Customer Maintenance Options sub window (same form) required.
Good News for the Microsoft Dynamics GP Community.
Friday morning (Perth Time) I had an email from Terry Heley from Microsoft with a link to a pre-release (ISV Drop) of the upcoming Microsoft Dynamics GP version 18.8 (October 2025) release. This download is provided to the ISV community to help them prepare for the final code when it is released.
This is the first post in a series of six articles discussing making additional Window Fields required and why the standard technique using Modifier does not always work.
For a field to behave as required, there are a number of different factors that must all fall into place. This article will explain the theory and what can go wrong. Links to examples with sample code will be published over the next week.
This is yet another update to the previous version of the change tracking project for Item cards:
Based on the version 4 project, this update for GP Power Tools Build 32 or later adds support for the Accounts window. Note it does require Build 32 or later to work.
This is yet another update to the previous versions of the change tracking projects for Customer and Vendor cards:
Based on the version 5 projects, this update for GP Power Tools Build 32 or later adds support for the Accounts window. Note it does require Build 32 or later to work.
If you need to customize Microsoft Dynamics GP or maintain existing customizations, David Musgrave from Winthrop Development Consultants will be running two extremely valuable development training courses before Community Summit 2025 and now it is time to register.
The conference will be held on the 19th to 23rd October 2025. There will be pre-conference GP Development training in the week before the conference as well as Academy days before and after the conference itself.
HURRY: LAST DAYS TO REGISTER
As of January 2026, Winthrop Development Consultants will be changing our product pricing to reflect the increases in functionality and features. It has been three years since the last time our pricing changed, and the world economy has also changed significantly in that time.
We have released multiple builds of all of our products in the last three years and will continue to support and develop our products moving forward.
This is another update to the previous version of the change tracking project for Item cards:
Based on the version 3 project, this update for GP Power Tools Build 32 changes the project to use a Custom Table and Custom Table Buffer calls rather than SQL Scripts and Parameter Lists. So, it does require Build 32 or later to work.
This is another update to the previous versions of the change tracking projects for Customer and Vendor cards:
Based on the version 4 projects, this update for GP Power Tools Build 32 changes the project to use a Custom Table and Custom Table Buffer calls rather than SQL Scripts and Parameter Lists. So, it does require Build 32 or later to work.
Winthrop Development Consultants is extremely excited to announce that Build 32 of GP Power Tools (GPPT) for Microsoft Dynamics GP was released on 20-Jun-2025, with a minor fix released 22-Jun-2025*.
This amazing build includes new features for every module in GP Power Tools. The build also includes many enhancements and improvements to existing functionality across the entire product.
This article lists the major new features and enhancements. It won’t list everything but to give you an idea of how much has been added, the user guide manual has grown from 833 pages in build 31 to 882 pages in build 32.
Today, we have an interesting support case where the installer for a Winthrop Development Consultants product failed to complete with the following error message:
Thanks to Noah Moseley for inviting me to be part of his Presenter Spotlights Podcast series.
We had a fun time discussing many topics including Microsoft Dynamics GP development and customization, the End of Support announcement, the training and sessions I will be presenting at Community Summit 2025, and finally Australian chocolates, Tim Tams and Vegemite!
Winthrop Development Consultants is taking part in the upcoming GP Demo Day by The ISV Society on 28th May 2025 at 1:00pm (US Eastern Time).
Join us and see how the new GP Power Tools Form Control module helps you adapt Microsoft Dynamics GP to your exact business needs—with little to no code.
Want to learn how to get the most out of GP Power Tools? Discover all the benefits and how you can employ them in your systems? GP Power Tools is the ultimate suite of tools to get the most out of your Microsoft Dynamics GP system, regardless if you are a user, a system admin, a consultant, a developer or a database administrator.
I am pleased to announce that as well as the Dexterity Training (during the week before the conference), there will also be GP Power Tools training offered at Academy at Summit in the days before Community Summit in Orlando, Florida, USA.
HURRY: LAST DAYS TO REGISTER
There is always lots of new functionality and enhancements to cover with the release the latest builds of GP Power Tools. It has features that will benefit all users of GP regardless of the level of the technical experience.
Update now to the latest builds for your version of Microsoft Dynamics GP.
This article provides advanced warning that old builds of Winthrop Development Consultants products for versions GP 18.0. or later will be discontinued at the end of August 2025 and will no longer be able to renew their subscriptions.
It is vital the customers update their installs of our products to get all the new fixes, features and enhancements that their annual subscription entitles them to.
With the release of GP Power Tools Build 31 including the new “No Code/Low Code” Customization Form Control Module, Winthrop Development Consultants are offering a discount on the annual subscription fees to all customers who have the entire suite of modules.
Now is the time to ensure that you are running the latest build of GP Power Tools on your system AND ensure your subscription includes all the modules available.
I have been meaning to write this article for quite a while. The Batch Posting Service Toolkit (BPST) is a product created by Winthrop Development Consultants to provide a variety of methods for posting, maintaining, transferring batches, etc.
The API’s (Application Programming Interface) can be called externally as a Service Based Architecture (SBA) Web Service (for GP 2015 or later), or from inside the Microsoft Dynamics GP application using Dexterity, Visual Studio Tools (via C# or VB.Net) or via GP Power Tools.
The Batch Posting Service Toolkit is exactly that, a toolkit designed to be called by a developer and so it does not have an interface (except for testing the API). However, you can use the Scheduling functionality in GP Power Tools to post batches on a scheduled basis, read on for more details ….
Scheduling or automating tasks in Microsoft Dynamics GP is a common request, so this example demonstrates a method that can be used to run any process on a scheduled or automated basis using GP Power Tools.
The specific example we will be using is running an Inventory Item Reconcile on items that have been flagged as needing reconciliation. This code was developed in conjunction with Arthur Achilleos, who has agreed for it to be published.