Click here to
Subscribe to
our Newsletter
Development related Posts
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.
GP Power Tools has very powerful and flexible Automatic Logout functionality to gracefully log idle users out of Microsoft Dynamics GP. However, this feature requires the user to be idle for a specified period before it will attempt to logout.
As an Administrator there are times where you would like users to exit Microsoft Dynamics GP immediately and don’t want to wait for Automatic Logout to activate. The sample project in this article makes this possible.
Previously, we have discussed controlling the Report Destination Dialogs and even External Dialogs using GP Power Tools but have not published any examples of controlling the standard System Dialogs shown when the warning, error, ask() or debug commands are used in Dexterity.
This example shows how GP Power Tools adds this functionality not normally available for use with Dexterity. Visual Basic for Applications and Visual Studio Tools both have the ability to trigger before and after Modal Dialogs, but Dexterity does not. GP Power Tools adds the functionality with its Modal Dialog Focus Triggers.
During the Dexterity Fundaments Bootcamp training, which was run in the week prior to the Community Summit 2023 conference, one of the attendees came up with an issue using the Multicurrency Access Setup window in Microsoft Dynamics GP.
Their problem is that the list of companies shown on the right-hand scrolling windows are unsorted and the customer has over 300 companies. This makes using this window extremely frustrating and slow. They already owned GP Power Tools and wanted to use it for a fix.
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:
I have been approached a couple of times with the request to place a QR Code (Quick-Response Code) onto a Microsoft Dynamics GP Report Writer report.
My initial response was that it was not possible as there is no way to include a dynamic image in a report. Only static images (such as logos) can be stored in the dictionary and added to reports.
But then I found online a couple of vendors selling QR Code True Type fonts….
We are seeing more and more sites realizing the potential of using GP Power Tools – Developer Tools module as their platform for custom development for customizations, tweaking and fixing behavior of code within Microsoft Dynamics GP.
Many customers are using GP Power Tools (GPPT) to replace their unsupported Visual Basic for Applications (VBA) customizations, which is great as GPPT is the best solution for replacing VBA, Dexterity and Visual Studio Tools addins. It offers many benefits over other development tools.
This week I was asked if GP Power Tools could automatically handle the login to email dialogs. Initially, I was thinking that this would not be possible as the login dialogs for both the Exchange Web Service and Multi Factor Authentication modes are not Dexterity based.
Then I decided to experiment with the .Net SendKeys Class using a .Net Execute script in GP Power Tools to see if the dialogs could be controlled by using code to insert keystrokes into the keyboard buffer.