As mentioned in my previous post, we needed a new build of the Support Debugging Tool for Microsoft Dynamics GP to work properly with the released build of Microsoft Dynamics GP 2010.
Releasing another build gave me the opportunity to include some enhancements that were suggested by my beta testers and the attendees at Microsoft Convergence Atlanta 2010.
The new build is now completed and available for download. I think the community will love the changes made, I know I do.
Below is a summary of the changes made for releases 9.00.0013, 10.00.0013 and 11.00.0013, I have divided them into logical sections:
Thanks to Mariano Gomez and Leslie Vail who came up with the Company Color Themes and the Security Information Resource window ideas (respectively).
For downloads, please see the Support Debugging Tool Portal Page:
Support Debugging Tool Portal
The Support Debugging Tool is a custom built tool to provide additional capabilities to troubleshoot issues and is not part of the standard Microsoft Dynamics GP released application. Technical support for this tool is not handled via the standard support systems and instead is provided via the public Microsoft Dynamics GP Community Forum. You can use the link below to access the forum:
To assist the partners and Microsoft employees who monitor the forum for these questions, please prefix any subject lines with the initials "SDT: ".
For more information, please see the Support Debugging Tool Portal Page:
Please post your feedback on what you think of this build and what you would like to see in the future.
16-May-2013: Updated More Information and Downloads to link to Support Debugging Tool Portal page.
Posting from DynamicAccounting.net
Posting from Inside Dynamics GP Blog
Posting from Victoria Yudin
Thanks Mark, good to see you using the Support Debugging Tool.
What a great tool for troubleshooting.
I was looking for a problem with customised dex code were particular settings were changed on a window, and then strange things happened.
I installed the Suport Debugging Tool and found the answer quicker then the install took.
The problem was caused by Field Service being installed and dex code from FS changed our values.
The script showed where the FS dex was running, so we were able to isolate.
Thanks for the feedback. It is appreciated. Make sure you have a play with all the other features available from both standard and advanced mode.
PLEASE READ BEFORE POSTING
Please only post comments relating to the topic of this page.
If you wish to ask a technical question, please use the links in the links section (scroll down, on right hand side) to ask on the Newsgroups or Forums. If you ask on the Newsgroups or Forums, others in the community can respond and the answers are available for everyone in the future.