Support Debugging Tool Build 14 released

David Meego - Click for blog homepageIt has been a while since we had a new build of the Support Debugging Tool for Microsoft Dynamics GP. So we have decided to release Build 14.  This is primarily a maintenance release with bug fixes, minor enhancements and a couple of new features.  This build can be installed over the top of any existing installed build without needing to remove the old build first.

Please note that this is the final release for version 9.00.

Below is a summary of the changes made for releases 9.00.0014, 10.00.0014 and 11.00.0014, I have divided them into logical sections:


  • Changes to Reject Script functionality in Advanced Debugging Mode to restore fields to their previous values.
  • Changes to Reject Script and Reject Record functionality so it can be controlled by using the OUT_Condition variable.
  • Fixed Non-logging triggers disabling Manual Logging Mode and Automatic Debugger Mode.
  • Fixed Security Information Show Resources Window showing Resource ID and Dictionary ID in incorrect columns.


  • Added Ctrl-R as Shortcut Accelerator Key for Raise All Windows (v10.0 or later).

  • Shift Company Color data storage from DUOS to coUserDefaults table, with automatic backwards compatibility.


  • Changes to minimise Suppport Debugging Tool scripts captured when turning on and off script logging.


  • Added support for Temporary tables into the Table Explorer window in the Resource Explorer.
  • Added support for Temporary tables into the Resource Information window.
  • Added text to Dex.ini Changes window shown at login to identify it as a Suppport Debugging Tool feature.
  • Added User Account Control (UAC) check when attempting to un-install Support Debugging Tool.
  • Added User Account Control (UAC) check when move products or deleting products in the launch file using Dictionary Control.
  • Added User Account Control (UAC) check when unchunking during installation.
  • Added User Account Control (UAC) state to the System Status report form ScreenShot.


  • Added Table Keys information to Table Explorer window in the Resource Explorer.
  • Added Table Keys lookup window to Resource Explorer.

  • Added Display Keys button to Resource Information window when in Table and Field mode.
  • Added Keep Focus and Restore Value options to Reject Script functionality in Advanced Debugging Mode.



For downloads, please see the Support Debugging Tool Portal Page:

Support Debugging Tool Portal


Support Information 

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: ".


More Information

For more information, please see the Support Debugging Tool Portal Page:

Support Debugging Tool Portal


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.

Comments (13)

  1. David Musgrave says:

    Post from Vaidy Mohan and Dynamics GP – Learn & Discuss…/support-debugging-tool-sdt-build-14.html

  2. David Musgrave says:

    Posting from Mark Polino at…/support-debugging-tool-build-14.html

  3. Leslie says:

    Hi David,

    As usual, another fabulous release! I spent a good time yesterday walking a client through the features of the tool. Eyes and smiles got bigger and bigger!

    OK, I have a wish. I would love to have a way to 'protect' a peice of script or SQL query such that a 'non-advanced' user could run it. Ideally I could use parameters in the query that the user could fill in and then execute. It's want, want, want from me :)!

    What do you think?


  4. David Musgrave says:

    Hi Leslie

    You could write this using the Runtime Execute window to ask the questions via system dialogs and then put in a script from SQL Execute, adjust the parameters and execute the script.

    The only think we don't have is the ability to prevent editing.


  5. David Musgrave says:

    Posting from Mark Polino at…/support-debugging-tool-is-kuntz.html

  6. Tyler says:

    Hi David,

    I was excited to see that you added support for displaying Table Keys to the Resource Explorer included in this tool. I'm curious how you worked around the issue of Table_GetKeyInfo only working within the Core Dynamics Dictionary. I've been searching for a way around this same issue and haven't had much luck, any chance you can let us know how you did it?


  7. David Musgrave says:

    Hi Tyler

    For GP 2010 onwards you can use the Table_GetKeyOption() function.

    For earlier builds, there is the getTableKeyAtPosition() of form XTableInformation; function.

    Below is an excerpt from the SDT's code:

    #if MBS_PROD_MAJ >= 11 then
      l_duplicates = Table_GetKeyOption(IN_DictID, IN_Table_Name, IN_KeyID, KEY_OPTION_ALLOW_DUPLICATES);
      l_primary = Table_GetKeyOption(IN_DictID, IN_Table_Name, IN_KeyID, KEY_OPTION_SQL_PRIMARY);
      l_unique = Table_GetKeyOption(IN_DictID, IN_Table_Name, IN_KeyID, KEY_OPTION_SQL_UNIQUE);
      l_clustered = Table_GetKeyOption(IN_DictID, IN_Table_Name, IN_KeyID, KEY_OPTION_SQL_CLUSTERED);
      { if IN_DictID = DYNAMICS then
        Table_GetKeyInfo(IN_ResID, IN_KeyID, l_duplicates, l_modifiable, l_compress, l_primary, l_index, l_unique, l_clustered);
      end if;

      getTableKeyAtPosition (IN_Table_Name, IN_DictID, IN_KeyID, l_key_name, l_duplicates, l_modifiable, l_compress, l_primary, l_index, l_unique, l_clustered) of form XTableInformation;
    #end if


  8. Phil says:

    Great job at Convergence 2011.  Can't wait to use this tool.  I guess I missed the release of this the past couple of years.

Skip to main content