Click here to
Subscribe to
our Newsletter
This is the sixth 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 Purchase Order Entry – Purchasing Vendor Detail Entry sub window (separate form) required.
This is the fifth 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 Salesperson ID field on the Sales Transaction Entry – Sales Customer Detail Entry sub window (separate form) required.
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