Support Debugging Tool Build 17 hotfix released

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 (http://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.

Well, as much as I try to ensure that there are not any bugs in the code, I managed to introduce one.

So this hotfix build fixes the bug which can cause the two Support Debugging Tool buttons to appear multiple times on the Standard Toolbar.

I also fixed an issue with the SQL Profile Trace setup where it can generate SQL errors if the system has users in the SY_Users_MSTR (SY01400) table which don’t exist as SQL Logins. This situation can happen when databases are restored to a different SQL Server.

If you have a previous build (including the original build 17) installed, please just install this update over the top of the existing code, no need to uninstall first.

Below is a summary of the changes made for releases 10.00.0017, 11.00.0017 and 12.00.0017, dated as Last Modified: 25-Jan-2013:

Fixes

• Fixed repeated creation of Screenshot and Support Debugging Tool Toolbar buttons on the Standard Toolbar.
• Fixed SQL Profile Trace setup errors when user exists in SY01400 table but does not have a SQL login.

More Information

For more information, please see the GP Power Tools portal, which replaced the Support Debugging Tool Portal.

• GP Power Tools Portal

Please post your feedback on what you think of this build and what you would like to see in the future.

Thanks to Robert Cavill for his assistance with this build. Thanks also to Kelly Youells for getting the files on PartnerSource updated.

David

16-May-2013: Updated More Information and Downloads to link to Support Debugging Tool Portal page.

This article was originally posted on the Developing for Dynamics GP Blog and has been reposted on http://www.winthropdc.com/blog.