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:

• #GPPT Making Window Fields Required and Why It Does Not Always Work

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.

Continue reading →

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:

• #GPPT Making Window Fields Required and Why It Does Not Always Work

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.

Continue reading →

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:

• #GPPT Making Window Fields Required and Why It Does Not Always Work

This example uses GP Power Tools code to make the Substitute Item 1 field on the Item Maintenance Options sub window (same form) required.

Continue reading →

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:

• #GPPT Making Window Fields Required and Why It Does Not Always Work

This example uses GP Power Tools code to make the Tax Registration Number field on the Vendor Maintenance Options sub window (same form) required.

Continue reading →

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:

• #GPPT Making Window Fields Required and Why It Does Not Always Work

This example uses GP Power Tools code to make the Tax Registration Number field on the Customer Maintenance Options sub window (same form) required.

Continue reading →

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.

Continue reading →

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.

Continue reading →

A recent GP Power Tools customization project for Microsoft Dynamics GP which I assisted a customer to create, ensures that a GL Account Number is entered on each line of a Purchase Order Transaction.

The customer for which this project created for has allowed it to be published on the blog to benefit anyone else who would like similar functionality.

Continue reading →

Using the GP Power Tools – Developer Tools module for customization is a great method of automating processes in Microsoft Dynamics GP as well as customizing behavior to meet the requirements of your business.

Many customers are also using GP Power Tools to replace Visual Basic for Applications now that it is “End of Life” and unsupported.

I was recently asked how to hide a window opened and closed as part of an automation using GP Power Tools. This article explains the techniques you can use to open a window as hidden.

Continue reading →