Click here to
Subscribe to
our Newsletter
This is a further update to the previous version of the change tracking project for Item Cards:
Based on the version 2 project, this update adds optional emailing of the changes made to a specified address.
This is another update to the previous versions of the change tracking projects for Customer and Vendor cards:
Based on the version 3 projects, this update adds optional emailing of the changes made to a specified address.
A few years ago I published an article showing you can use a GP Power Tools custom RW Function to execute a SQL query and return data to a report. This article used some techniques which were valid at the time and while they still work, there are better and faster methods available in the later GP Power Tools builds.
Here is the link to the original article:
Following on from the article published on Friday about why Microsoft Dynamics GP uses many 8 upper case character table and column names:
This article consolidates many of the articles written about using MS SQL Server with Dexterity and also publishes original documentation from 1999 on how SQL Server support was added to Dexterity.
Today, I was asked by a consultant how to parse specific data out of the record note associated with a transaction or master record in Microsoft Dynamics GP using a SQL Server query.
GP uses the SY_Record_Notes_MSTR (SY03900) Record Notes Master table to store a text field of up to 32767 characters linked to master or transaction record using the Note Index (NOTEINDX) field. The next available Note Index is stored in the SY_Company_MSTR (SY01500) Company Master in the system (DYNAMICS) database and is assigned to new records when they are created.
This is a further update to the previous versions of the change tracking projects for Customer and Vendor cards:
Based on the version 2 projects, this update adds tracking to the Vendor and Customer EFT Bank Maintenance windows.
This article has two purposes. The first is to highlight a very useful script published by Michael Krasivsky from The Resource Group back in 2016. The second is to explain how easy it is to use the GP Power Tools SQL Execute Setup window to execute scripts against multiple databases.
Microsoft Dynamics GP provides access to all the SQL Resources (Tables, Views, Stored Procedures, etc.) using the DYNGRP SQL role. For this technique to work correctly, all GP users need to be assigned to the DYNGRP role and all SQL objects need access “Granted” to the same DYNGRP role.
GP Power Tools is a subscription based product. This means it needs current, valid Registration Keys to stay operational.
If you have written Mission Critical Custom Code using GP Power Tools – Developer Tools module, you will want to ensure that those triggers and scripts stay active at all times and if the registration fails for any reason that you are notified immediately.
After the publishing of the GP Power Tools projects for tracking changes to Customer and Vendor Cards, there have been requests for the same functionality for Item Cards.
Starting with the framework updated in the version 2 of the Customer and Vendor tracking projects:
I have created the same functionality for Item Cards. It is labelled as Version 2 so it stays in sync with the other trackers. Even though this is actually the first release, it is based on the Version 2 code.
This is an update to the previous version of the change tracking projects for Customer and Vendor cards:
Based on the original projects, they have been enhanced to add some more fields into the default fields tracked, add support for array fields, and add support for tracking Modifier Added fields.