web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Dexterity Debug Test M...
Microsoft Dynamics GP (Archived)

Dexterity Debug Test Mode security to custom window

(0) ShareShare
ReportReport
Posted on by Community Member

We recently upgraded from GP 9 to GP2010 including our dexterity environment.  All is well in production runtime.  In Dexterity we have a mix of modified windows and custom windows created by us in Dexterity.  In the Dexterity environment when I go into the Debug menu - Test Mode everything starts as expected and I log in.  When I attempt to open a custom window I get the security warning indicating I do not have security privileges to open the window.  All other windows (Dynamics and modified windows) open as expected.  The fact that it's a security warning tells me that GP recognizes that the window exists in the dictionary but it doesn't think I have security in Test Mode.  I'm trying to determine the cause of the issue and get it recitified and understand how security might be involved since in Debug mode it's a different dictionary than at runtime.  Any help is appreciated and please let me know what further information I can provide to help resolve this.

Thank You.

*This post is locked for comments

I have the same question (0)
  • Dave Dusek Profile Picture
    Dave Dusek Microsoft Employee on at

    Your security is set to your form but is it your form in your distributed dictionary.  So you have your custom dictionary loaded, security is set to that form.  That's why it works in production.  Now you are in test mode, only the dictionary you are currently in is loaded, and that has a product id of 0.  Security is set to your dictionary, product id is not zero, it's yours.  So you have to set security back to the dictionary you have open in test mode.  Then of course that will break your production environment, so you will have to change it back when done.  

  • Community Member Profile Picture
    Community Member on at

    Thank you Dave, I appreciate the quick reply.  One additional piece of information is that we have a GP account we use strictly for dexterity testing and do not use it to log into production runtime. That is, we use this dex account only in Debug test Mode, we don't use it in production.  So we intend to have security set appropriately for debug test mode.

    I agree/understand everything you said but I have one implementation question.  When you say "set security back to the dictionary you have open in test mode" I'm thinking I need to use Debug Test Mode to start GP and go into security that way so that it understands I'm dealing with the development dictionary.  Problem with this is that when I look for my custom window/form this way it is not listed for me to check.  Should I be seeing my custom window this way or should I be going about setting the security a different way?

    Thanks Again,

    Erik

  • Dave Dusek Profile Picture
    Dave Dusek Microsoft Employee on at

    Erik,  If the form is in the dictionary, and then you launch test mode, it will be listed in the security window, it has to be.   The problem is that you see all the gp stuff too, but it has to be there.  

  • Community Member Profile Picture
    Community Member on at

    Dave, I'm right with you and agree, hence I'm at a loss wondering why I can't see any of our custom windows (but only our custom windows).  I have checked out a form from source control and made a change to it so I'm cetain the form/window is in the dictionary. I was starting to wonder if our upgrade process went well but even if it didn't my window must still be in the dictionary and therefore should be visible in security.  I look up the dex (development) account in security that is assigned a single role.  That role is assigned a single task.  When I open the task setup with the right ID I set the product drop down to the dictionary I'm in (launched from Test Mode) and set the Type to Windows and set the Series appropriately (in the case Inventory).  I've triple checked this and gone through the other series just in case...  The security was all set through the upgrade process during the GP2010 installation which we did a lot of research in CustomerSource, web etc and have gone through this process before.  All the steps made sense and we elected to have the GP2010 installation bring the security forward.  I feel there might be something to this but I go back to the fact that the form is in the dictionary now.  Any direction you can point me in to look at, research etc is appreciated.  I'm a developer for Dexterity, SQL Server and Visual Studio (C#, C++, VB) so I'm very comfortable checking anything in the Dynamics database.

    Is it possible the issue lies with the Dynamics.Set file or Dex.ini I'm using in the Dexterity environment?

    Erik

  • Community Member Profile Picture
    Community Member on at

    A little more information to add.  When I enter Debug Test Mode as sa I can open the custom windows straight off with no issues.  This confirms the windows are in the dictionary and with enough privilege level they are accessible.  

    When using the development account I can add the custom window to shortcuts so there is visibility to it I just can't open it (but can if logged in as sa).  So all this goes back to some form of security issue.  Is there another way to approach security in GP 2010?  

  • Community Member Profile Picture
    Community Member on at

    For anyone that can add more insight, if I give my dexterity development account security to the Poweruser role then all is well and I can access all custom windows under the Dexterity Debug Test Mode.  This is consistent with all being well when loggin in as 'sa'.  However, I would prefer not to give a development unit test account PowerUser role unless that is the Micorosoft prescribed method.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans