Support Debugging Tool Build 12 released

David Meego - Click for blog homepageThis 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)

Some of you might have had a sneak peak at a few of the new features in build 12 of the Support Debugging Tool for Microsoft Dynamics GP when an early beta version was demonstrated at the Microsoft Dynamics GP Technical Conference 2009. Since then there have been many other changes and improvements.

Well now the new build is completed and available for download.  I am really proud of this build as it “finishes off” a number of features and also fixes some of the issues found with the previous builds.

Below is a summary of the 50 or so changes made for releases 8.00.0012, 9.00.0012, 10.00.0012 and 11.00.0012, I have divided them into logical sections:

Fixes

  • Fixed Company Based color schemes not changing when switching companies.
  • Fixed Company Based Color schemes being reset even when disabled in Administrator Settings.
  • Fixed Error message when using SQL Execute window against the System Database.
  • Fixed Login dialog appearing when using “Start Logging on next startup only” option.
  • Fixed incorrect colouring of static text in window toolbar for Resource Explorer and SQL Execute Windows.
  • Fixed handling of v10.0 table security for Resource Information, Security Profiler and Security Information (v10.0 only).
  • Fixed looping caused by Security Profiler attempting to open when access to the Security Profiler window is denied.
  • Fixed security access error when Support Debugging Tool menu window attempts to open automatically when access is denied.
  • Fixed Resource Information window Open Button to allow it to work when resource name contains spaces.
  • Fixed Default Path for three logging facilities to use dex.ini path if specified.
  • Fixed issue where file dialogs were causing application to crash.

Enhancements

  • Allow ScreenShot to email System Status and optional files without windows being selected.
  • Added Network User Name to Screenshot’s System Summary Report.
  • Added “Show Debug Messages on next login” option to Dex.ini Settings window.
  • Added new ScriptLogEnhanced Dex.ini setting to Dex.ini Settings window.
  • Added control of Windows Toolbar color to Company Based color schemes (v10.0 only).
  • Added Report Explorer to Resource Explorer for use with the Resource Information window.
  • Added Series All to the Report Explorer window to show all reports regardless of series.
  • Added Series All to the Table Explorer window to show all tables regardless of series.
  • Added Table Groups to the Table Explorer window to show tables in their logical table groups.
  • Added Table Group All to the Table Explorer window to show tables regardless of the table group they belong to.
  • Added support for custom reports to Report Explorer and Resource Information windows.
  • Added User and Company tree to Security Information window.
  • Added Security Role, Security Task and Alternate Modified Forms and Report Views to Security Information window (v10.0 only).
  • Added Security Role (System Level), Security Task (System Level) Views to Security Information window (v10.0 only).
  • Allow Security Information window to be opened without a resource selected so that new views can be used.
  • Added ability to disable Modified forms and reports from the Dictionary Control Window.

Performance

  • Speed up Debugger Settings window Tab 1 (Debug) display code.
  • Removed pause caused when Resource Explorer is opened by initializing each explorer window when it is first used.
  • Performance improvements to XML Table Export and XML Table Import features. Approximately 25% faster.
  • Speed up loading of Lookup windows by only loading required table from setup file.

Usability

  • Added warning message to Security Information window when Security is not enabled for a company.
  • Remember Last Company Logged into using SQLLastCompany Dex.ini setting.
  • Added Apply Button to Dictionary Control window.
  • On SQL Execute window, moved Syntax information to an additional window to increase screen real estate.
  • Added better handling of notification messages when no data sets returned on SQL Execute window.
  • Added Seeding of Resource Explorer windows from Resource Information Window and XML Table Export window.
  • Improved Usability of Resource Explorer window to allow tree selection to be used when no items selected in list.
  • Added Tooltips to display file paths, useful when the path is longer than the visible areas of the field.
  • Added Zoom to Resource Information window from Security Profiler window using double click or context menu.

Features

  • Added Table handling for Dex.ini Configuration window.
  • Added Dex.ini Configuration window and processor on login.
  • Added Administrator Default Dex.ini Settings to Dex.ini Configuration window.
  • Added Workstation Configuration Override setting to Dex.ini Configuration window.
  • Added additional handling to Dex.ini Settings window when changing settings controlled by Administrator.

  • Added audit information (Created Date, Modified Date, User ID, Windows User) to setup tables and add additional table for XML Table Export Profiles.
  • Added Profiles to XML Table Export window to allow multiple sets of tables to be setup and exported.
  • Added Report to XML Table Export window.

  • Updated Configuration Export/Import to support XML Table Export Profiles.

Please see Support Debugging Tool for Microsoft Dynamics GP 2010 Beta for what is new in the v11.0 build and in the updated builds for v9.0 and v10.0.

Acknowledgments

A big thank you to the beta testers. A special thanks to Mariano Gomez and Leslie Vail who helped with deciding what fixes and features we needed to include with this build while we were preparing for the troubleshooting session at the Microsoft Dynamics GP Technical Conference 2009.

More Information

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

Please post your comments on what you think about the new features. Also tell us what other features to assist in supporting and debugging Microsoft Dynamics GP you would like to see in the Support Debugging Tool.

David

27-Feb-2010: Added details and link for Support Debugging Tool v11.0 for Microsoft Dynamics GP 2010.

10-Mar-2010: Added link for Support Debugging Tool Portal page.

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.

25 thoughts on “Support Debugging Tool Build 12 released

  1. Hi David,
    Do you have Demo for this Latest Build Support Debugging Tool.
    Or The Demo from Microsoft Dynamics GP Technical Conference 2009.

    Like

  2. Hi Sukhdeep
    We did create a demo video after the Microsoft Dynamics GP Technical Conference 2009 in Fargo, but it was for internal use only.
    We are looking to create new videos of the two sessions Mariano and I presented at that conference. Once they become available I will post the details on the blog.
    The tool is really easy to use, so just download it and have a play.
    David

    Like

  3. Thanks David,
    The day I came back from Microsoft Dynamics GP Technical Conference 2009 , I am using this tool, This is really very use full tool for developement as well, I always found very helpless for writting some thing for 3rd Party dic but with this tool I am doing very good.
    Can you please guide me a bit to read temp tables or actual Table Buffer at runtime?

    Like

  4. Hi Sukhdeep
    The Support Debugging Tool’s Automatic Debugger Mode Triggers for database or table events can capture the current record or entire table for any table and export the data to XML.
    If you are talking about getting access to the table buffer of a 3rd party product using Dexterity, there is a method for capturing a reference to the table buffer explained here:
    http://blogs.msdn.com/developingfordynamicsgp/archive/2009/11/23/accessing-a-table-buffer-when-it-is-not-passed-as-a-parameter.aspx
    Also look at the Cross Dictionary Development conference materials here:
    http://blogs.msdn.com/developingfordynamicsgp/archive/2008/07/24/cross-dictionary-dexterity-development.aspx
    David

    Like

  5. Hi Sukhdeep
    Without access to the source code you would only be able to get a generic data type from the script log.  You should be able to see if it is a date, time, integer, decimal or string/text from the parameters shown on the script log.
    If this is a MS product, there is some information for some of the MS addon products in the SDK.
    If this is an ISV product, you can always contact the developer for information.  
    If you are interested in integrating with specific scripts, you can always ask for the parameter list from the developer (MS or ISV).
    David

    Like

  6. Hi David,
    I use this tool often for Resource descriptions. Since I am usually looking up tables – I have to change the Resource Type to ‘Tables and Fields’. Is there a switch or something that will default the setting to ‘Tables and Fields’?
    Right now I use a macro to launch it, but I thought it wouldn’t hurt to ask.
    Also, you told be why you defaulted the settings to ‘Exact Match’ and ‘Case Sensitive’, but I forgot. If it’s quick, would you mind refreshing my memory?
    Your a Rock Star!  This is the greatest tool ever made when it comes to Dynamics!
    See you in Atlanta!
    Leslie

    Like

  7. No, there isn’t any kind of setting that will store this for you.  However I seem to recall there IS the old push pin on the window so that once you choose an item in the list it doesn’t close the window.  It makes it easier to check multiple tables.  It should be fairly simple to automate the setting in the SDT to always open in the view (better yet, remember the view it was set to).  Or just default the pin so you only have to set it the once per session.  Or stick with your macro until the above would happen.

    Like

  8. Hi Leslie
    Exact Match and Case Sensitive allows Dexterity to perform direct lookups to get the results of the resource search.
    Any other search mode requires a scan of each dictionary, resource by resource until a match is found.  While reasonably fast on a good machine, it is not the instant response that the Exact Match, Case Sensitive search gives.
    Also Exact Match, Case Sensitive was the only behaviour before the extended searching functionality was added to the window.
    Look for the remembering of modes in future builds.
    David

    Like

  9. Hi David,
    I Have one question regarding GP users, As GP Users Password is encripted, Is it possible to use the same user for eConnect/Web Services application ?
    I mean if i create a login screen in C#, Is it ok to pass that User-Password to econnect?
    Thanks

    Like

  10. econnect doesn’t use user/password, it uses windows auth.
    web services also doesn’t matter because it uses your windows user/password and not your sql gp credentials.

    Like

  11. Thanks Patrick  for quick reply,
    I mean some thing else,
    Say i import SOP Orders to GP by Using either eConnect/Web Services.
    Now i want to do some more by Connecting to SQL Server, now i need GP User Credentials.
    Is there a way that i can use same User name and Password as used in Gp?
    (Gp encripts the password)

    Like

  12. Yes but you’d need to use gpconnnet.dll.  for that you’d have to log a dexterity or vstools support case to get the documentation and the reg keys in order to use it.

    Like

  13. Hi Dave,
    Do you know how (or it is possible) to have access to auto generated number in Integration Manager? I need to do some work in the After Document script.
    Cheers

    Like

  14. Hi Philip
    This is not the correct location or a relevant post to ask this question. Please use the newsgroups or forums. Links on the right hand pane.
    David

    Like

  15. Hi Sant Marry
    There is no danger from the Support Debugging Tool as all features that can update or view data are protected as Advanced Mode Features and can only be accessed by a user with sysadmin sql permissions.
    Anyhow the SDT does not interface with VBA in any way and does not provide any password related functionality.
    David

    Like

Please post feedback or comments

This site uses Akismet to reduce spam. Learn how your comment data is processed.