Click here to
Subscribe to
our Newsletter
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
We have seen a few support cases recently about a change to the Void Historical Payables Transactions and Void Open Payables Transaction windows in Microsoft Dynamics GP 2013 Service Pack 2.
Note: This issue is fixed in GP 2013 R2.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
IMPORTANT NOTICE: The Support Debugging Tool is now GP Power Tools from Winthrop Development Consultants (https://winthropdc.com/GPPT)
It has been a way too long between releases, but I am finally ready to release Build 18 of the Support Debugging Tool for Microsoft Dynamics GP for versions 10.0, GP 2010 (v11.0) and GP 2013 (v12.0).
This is a reposting of an article Patrick Roth originally wrote on my Developing for Dynamics GP blog.
This will be a 2-for-1 post today as the example given solves a frequently asked question and was used to solve a customer issue.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
I had a case recently where the customer’s auditors were asking the customer to prove the version and build of Microsoft Dynamics GP was the same as the version they claimed it was. Basically, the auditor said “provide me proof that you are running GP X SP Y”.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
This is an update to the original Using Named Printers with Terminal Server post from August 2008.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
IMPORTANT NOTICE: The Support Debugging Tool is now GP Power Tools from Winthrop Development Consultants (https://winthropdc.com/GPPT)
Following on from the release of the Support Debugging Tool Build 17 hotfix, I am releasing a hotfix 2 build.
It turns out that some of the changes in the way the Support Debugging Tool adds buttons to the Standard Toolbar were still not perfect. We had a few reports that when the SDT dictionary was installed, newly created users would be missing their menus. The solution was to remove the SDT from the system and recreate the user, or to use SQL to drop the contents of the menu and toolbar tables, which will force them to be recreated.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
IMPORTANT NOTICE: The Support Debugging Tool is now GP Power Tools from Winthrop Development Consultants (https://winthropdc.com/GPPT)
Just before I went on leave over Christmas and New Year, I announced the release of the Support Debugging Tool Build 17.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
IMPORTANT NOTICE: The Support Debugging Tool is now GP Power Tools from Winthrop Development Consultants (https://winthropdc.com/GPPT)
With the release of Microsoft Dynamics GP 2013, I am pleased to announce the release of Build 17 of the Support Debugging Tool for Microsoft Dynamics GP for versions 10.0, GP 2010 (v11.0) and GP 2013 (v12.0).
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
As promised in my post Quick Tip: Creating a Splitter control between panes of a window with Dexterity, I have updated the concept of my previous post: Resizing SmartList TreeView and ListView panes using the Support Debugging Tool to use a Splitter control rather than selecting a percentage via a menu option.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
A recent support case again highlighted how useful the Support Debugging Tool for Microsoft Dynamics GP can be. This time the customer was having an issue where Microsoft Dynamics GP was crashing while they were working in a specific window.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
A while back, I posted some articles which used the Support Debugging Tool and non-logging Automatic Debugger Mode triggers to “encrypt” data.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
While we are troubleshooting error messages from the Support Debugging Tool, I had another one reported last week.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
This is another issue which can come up every now and then when installing the Support Debugging Tool.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
This issue with the Support Debugging Tool has occurred a few times recently after installing the latest version of the Support Debugging Tool.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
While I am updating examples, I have made some changes to the Adding Window Size and Position Memory using the Support Debugging Tool sample code.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
A little while ago, I posted an example of Obscuring Table Data Fields using the Support Debugging Tool.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
This minor issue with the Support Debugging Tool has raised its head a few times, so I thought I would explain what is happening and how to resolve it.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
My colleague, Allan, had a case recently where the customer had noticed that the Credit Card Number field stored on the Customer Master table at the SQL Server level was not encrypted or obscured and could be seen by anyone who could access the data.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
This article is another Support Debugging Tool Non-Logging Trigger example and is a follow up to two previous articles:
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
As a follow on to the article: Using Support Debugging Tool Non-Logging Triggers, I thought I would post a few small examples of how Non-Logging Triggers can be used for simple customizations.