Recently, Mike from Thybar Corporation contacted me about an issue he was seeing in Microsoft Dynamics GP v18.7 with General Journal document attachments.
Journal Entry attachments that had been added before upgrading Microsoft Dynamics GP to v18.7 could no longer be viewed from the Journal Entry Inquiry window after the upgrade.
Over time the amount of data stored by your Microsoft Dynamics GP system can get quite large. Without buying new hardware, there is a simple way to make your system faster and decrease the space used to store your databases.
This is where a couple of the features of the Database Module of GP Power Tools come in to help. This is article 3 of 3 in the series.
Over time the amount of data stored by your Microsoft Dynamics GP system can get quite large. Without buying new hardware, there is a simple way to make your system faster and decrease the space used to store your databases.
This is where a couple of the features of the Database Module of GP Power Tools come in to help. This is article 2 of 3 in the series.
Over time the amount of data stored by your Microsoft Dynamics GP system can get quite large. Without buying new hardware, there is a simple way to make your system faster and decrease the space used to store your databases.
This is where a couple of the features of the Database Module of GP Power Tools come in to help. This is article 1 of 3 in the series.
Welcome to the eleventh article as an update to the series of articles that explains in detail the steps to add a user defined custom field to a window using Modifier, Report Writer and GP Power Tools to add the business logic.
The series should be read in order starting with the introduction article:
In this article we will show how to use Custom Tables (added in Build 32) to store data rather than the DUOS table. In the previous articles we included the Customization Maintenance packages and showed how to use manual SQL tables.
Welcome to the tenth article as an update to the series of articles that explains in detail the steps to add a user defined custom field to a window using Modifier, Report Writer and GP Power Tools to add the business logic.
The series should be read in order starting with the introduction article:
In this article we will show how to use manual SQL tables to store data rather than the DUOS table. In the previous article we included the Customization Maintenance packages. In the following article we will show how to use GPPT Custom Tables (even better than manual SQL tables).
Welcome to the ninth article as an update to the series of articles that explains in detail the steps to add a user defined custom field to a window using Modifier, Report Writer and GP Power Tools to add the business logic.
The series should be read in order starting with the introduction article:
In this article we will provide updates to the project adding the modified window and report to the project. In the following articles we will show how to use manual SQL tables and then GPPT Custom Tables (even better than manual SQL tables).
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.
This article is designed to help you perform a system audit on your Microsoft Dynamics GP system and is used as part of my Microsoft Dynamics GP Systems Audit session in the first week of the Dynamics GP Strategic Planning Digital Summit being held each Wednesday for the next 5 weeks.
Identifying the installed products in the system is fairly easy as you can look at the Dynamics.set launch file to see all the Dexterity product dictionaries loaded.
However, having a product loaded in a system does not necessarily mean that it has been used.
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.
GP Power Tools build 30.2 added a feature to check the installed SQL Server version against the minimum supported version, as per the published System Requirements for Microsoft Dynamics GP, and will warn on login if the version of SQL Server does not meet the minimum system requirements.
This is another “Must Have” free customization example for you Microsoft Dynamics GP system when you have GP Power Tools – Developer Tools module.
When creating new Customer, Vendor and Item cards, it is possible to include certain characters in the ID fields which can cause issues with Microsoft Dynamics GP, its ISV products and integrating products.
GP Power Tools has the ability to capture SQL Profile Traces as one of the five different types of logs it can generate from Microsoft Dynamics GP.
To achieve this, GP Power Tools needs to change some permissions on the SQL Server so that it can both generate the Trace programmatically and also copy the resulting files to the shared Logging Folder.
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.