HR and Payroll Navigation Pane issue

Patrick RothA while back, there were several posts in the public Dynamics GP newsgroup about that HR & Payroll Navigation button being 'messed up'.  Finding that odd, I looked at mine on 10.0 SP1/SP2 - I don't recall which - and noticed the same thing.  Unfortunately I don't recall exactly what what the issue, only that the area page wouldn't come up propertly like it did on the Sales, Purchase, etc buttons.

Checking with my colleagues here, I found that about half were OK and half impaired in some manner.

I remember doing a bit of investigation in source code and not being able to come up with a why this should happen.  However I did a bit of Dexterity work and fixed my own issue.

I ran across a copy of that post the other day and noted in the newsgroup that it was again messed up on my 10.0 SP3 system (the same instance from before - just upgraded to 10.0 SP3) and noticed that I appear to have all of the items for the HR & Payroll panel, just out of the expected order.  And that is why the area page doesn't appear right away since it isn't at the top of the list.

Thinking about it a bit and having to ferret out the solution again, I tried to think of a way to be able to deploy this solution to others.  The main question I faced was - how do you all execute some Dexterity sanScript easily and without me posting a chunk file with just a button on it?

The solution came to me rather quickly - the Support Debugging Tool.  While it can do all kinds of logging, the part we care about in this situation is the Runtime Execute piece. 

  1. The first step is to download the Support Debugging Tool and get the application installed.

  2. Once installed, log into GP as 'sa' or 'DYNSA' user or another user that has dbo access as that is required to get to the window we need.

  3. Open the Support Debugging Tool main window by choosing Microsoft Dynamics GP | Tools | Support Debugging Tool.

  4. From the Support Debugging Tool main window menu, choose Debugger | Dex.ini Settings

  5. From the Support Debugging Tools Options section, mark the Enable Debugger Advanced Mode Features checkbox.  Press OK to close the window.

  6. From the Support Debugging Tool main window menu, choose Debugger | Runtime Execute

  7. Enter in a Script ID - anything will do.  I called mine HRNAVPANE.

  8. Enter in a Script Name - again anything will do.  I entered HR & Payroll Nav Pane.

  9. For the context drop list, choose Microsoft Dynamic GP as the product.

  10. In the code section; enter the script below.
    Runtime Execute Script

  11. Press the "Execute" button at the bottom right.  This will execute the code successfully unless you didn't enter the code above correctly somehow.  This procedure will redefault the navigation pane information for the HR & Payroll navigation button.  It will not delete any custom lists that you may have personalized.

  12. At this point you are finished and you can save this code by pressing the Save button in the window or just clear it.  You can then also close the Support Debugging Tool window and exit GP.  You might want to save it in case this happens again on the next upgrade.

  13. When you log in again, you'll see that your HR & Navigation pane looks correct.  Or at least I presume it will since mine does now!


// Copyright © Microsoft Corporation.  All Rights Reserved.
// This code released under the terms of the
// Microsoft Public License (MS-PL,

Comments (5)
  1. Now that the secret is out… I have also used Support Debugging Tool to put in quick code for my customers that would otherwise require a chunk. Perhaps not the original intention, but it sure does work 🙂


    Mariano Gomez, MVP

    Maximum Global Business, LLC

  2. David Musgrave says:

    Hi Mariano

    The Runtime Execute window was designed to be able to run Dexterity sanScript scripts to fix data issues.  Sometimes using Dexterity code can be simpler or more efficient than writing SQL Queries to fix the data.

    The Support Debugging Tool allows both options with the Runtime Execute and SQL Execute windows.

    Using Automatic Debugging Mode Triggers in Non Logging mode was designed to be able to add extra triggers to use in conjunction with Automatic Debugging Mode, or to test triggers to see if they can fix an issue.

    A system administrator can use these non logging triggers to create simple customisations.


  3. Leslie Vail says:

    This is wonderful!  I’ve thought I would just need to wait for the service pack.  Thank you for sharing this fix.  I wonder if there is any way to change the layout so all of the navigation panes have ‘Cards’ on the upper right and ‘Transactions’ on the upper left. Compare Financial to Inventory to see what I mean.  Perhaps I haven’t been searching correctly and ‘the fix is out there’.


  4. Patrick Roth [MSFT] says:

    That is the funny thing – there is obviously a bug but the code that we run is cut right out of GP so you wouldn’t think there would be an issue or that the code would fix it.  But it does.  So odd – but I wasn’t that interested to debug through dynutils/dynamics source to see if i could figure out why it was happening.  Assuming it did since it doesn’t always.

    For the Inventory Area Page, that does seem to be a UI bug.  But it isn’t something that you can ‘fix’ permanantly.  When we build the area pages on the fly, we built them in order how we want them.  For whatever reason, that one has the items out-of-order.  I’m sure it wasn’t intentional.

    You could log a bug on it and the fix from our end will be easy.  As this is a cosmetic bug, it probably wouldn’t be a high priority fix but it is worth getting logged.

  5. Ritesh says:

    Nice post sharing information related to understanding Payroll Systems

Comments are closed.

Skip to main content