#GPPT Tracking changes to Customer and Vendor Cards Version 3

This is a further update to the previous versions of the change tracking projects for Customer and Vendor cards:

• #GPPT Tracking changes to Customer and Vendor Cards Version 2

Based on the version 2 projects, this update adds tracking to the Vendor and Customer EFT Bank Maintenance windows.

[Edit] Version 4 of the Customer and Vendor Change Tracking is now available:

• #GPPT Tracking changes to Customer and Vendor Cards Version 4

The design has not changed since version 2, we have just added an extra trigger for the EFT Bank Maintenance windows along with adding the Sub Type into the Parameter List.

Version 2 added support for Array Fields and Modified windows for Customer Maintenance, Customer Address Maintenance, Vendor Maintenance and Vendor Address Maintenance.

Below are screenshots of the two projects showing the components. Here is CUST TRACKING project:

And the VEND TRACKING project:

If you want to change the tracked fields, you can edit the triggers and change the Fields_* comma separated lists at the top (just scroll past all the variable declarations).

The Field names must be the Dexterity Technical Names. You can use the Resource Information window to display the Field Names. If you open it first and make sure it is in “Form, Window & Field” mode with the “Show currently selected Window and Field information” option selected. Or you can use the Tools >> Resource Information option available from any window.

Note: The single quotes should not be included in the comma separated list variables.

To make modified fields work, remove the // comment from the Fields_Modified variable declaration and put in a name for the field. It does not have to be the actual field name. Then edit the associated Runtime Execute script (same name as Trigger) to uncomment the code to run on the modified window (first { and last } ).

If you need access to data from the standard GP table for the window, you can uncomment the code that reads the table.

Then change the case statement to add your field name  (must match the name used in the Trigger’s Fields_Modified variable). Finally get the value from the window for FieldNew and read the value from the table for FieldOld. The Helper function for reading data from the DUOS (Dynamic User Object Store) is already in the code, but you could change this to read the data from other locations (including reading data from SQL).

WARNING: If you already have the previous versions installed, please make a note of the Fields included if you have changed the field lists before importing, so you can remake the changes after installing the updated projects.

Downloading and Installing

Download the example code, import using the Project Setup window (now possible for first time imports with Build 28.8 onwards), or use Configuration Export/Import window (for older builds):

• GP Power Tools Settings Cust Tracking.dbg.zip
• GP Power Tools Settings Vend Tracking.dbg.zip

The code will be active on next login or after switching companies, or you can use start the triggers manually from the Project Setup window.

More Information

For more information see:

• #GPPT Tracking changes to Customer and Vendor Cards Version 4
• #GPPT Tracking changes to Customer and Vendor Cards Version 3
• #GPPT Tracking changes to Customer and Vendor Cards Version 2
• #GPPT Tracking changes to Customer and Vendor Cards
• #GPPT Using GP Power Tools to track specific changes
• #GPPT Using GP Power Tools to track specific changes Revisited
• GP Power Tools Portal: http://winthropdc.com/GPPT
• GP Power Tools Samples: http://winthropdc.com/GPPT/Samples
• GP Power Tools Videos: http://winthropdc.com/GPPT/Videos

Hope you like the enhancement added with this version.

David

17-Jan-2024: Updated projects to Version 4 code.

This article was originally posted on http://www.winthropdc.com/blog.