Update: How to identify the Security Tasks and Security Roles using the Support Debugging Tool

David Meego - Click for blog homepageAdded to the Microsoft Dynamics GP Application Level Security Series.

I am still surprised how many times questions appear on the newsgroups and forums asking about which Security Tasks and Security Roles are needed to access a particular window. It has been a while since I posted anything about the Support Debugging Tool, and this seems like a perfect opportunity to show how simple it is to use the Support Debugging Tool to find this information.

This blog already contains two posts on this topic (links below), the first showing how to obtain the Security Tasks and Roles using the DEXSQL.LOG and a SQL query.  The second post uses the Support Debugging Tool to identify the window and then used the SQL Execute to run a similar query to the first post.  Since these posts were created the Security Information window as added to the Support Debugging Tool, and this window makes working with security even simpler. 

So, let's say I want to know how to grant access to the "Create Return" window which is accessed from the Additional menu on the Sales Transaction Entry (SOP_Entry) window. This window is particularly hard to find as it is not visible in the Sales series of the Microsoft Dynamics GP product or in fact any other product.

The steps below show how this information can be located quickly:

  • Open the Support Debugging Tool by selecting Microsoft Dynamics GP >> Tools >> Support Debugging Tool or pressing Ctrl-D.  From the main Support Debugging Tool window, click Options and select Resource Information.

Note: If your menu has less options, turn on Advanced Mode from the Options >> Dex.ini Settings window.

  • Once the Resource Information window is open, make sure that the Resource Type drop down list is set to Form, Windows & Fields mode. Then type "Create Return" into the Display Name field and press Tab. You can also search for the window using the Menu Explorer (using menu navigation) and Resources Explorer (using dictionary and series) lookup windows.

Notes: Changing the Search Mode and Case Sensitive settings allow searching on partial names.

  • Now that we have located the window and identified that the Create Return window is actually the SVC_RMA_Create_Return form in Project Series of the Field Service dictionary.  To find out how to access the window, click the Security button.

  • The Security Information window will open displaying the security information for the selected resource.  Expand the System Level node in the left pane to see the Security Tasks and Security Roles associated with the window. For our example the "Create Return" window is used by the TRX_FSS_RT01* Security Task and which in turn is used by the RT_Agent* and RT_Manager* Security Roles.  So for a user to have access they will need to be added to at least one of the two roles.

That's how easy it is.

While we have the Security Information window open, let's take a look at the what else you can see from this window:

  • The window opens with the currently logged on user and company selected. The top half of the left hand pane shows the access for that user and company.
  • Use the User ID and Company lookups to change the selected user and company, or you can select a user and company from the right hand pane.
  • Use the button drop down list from the heading of the left hand pane to change the selected resource.
  • Expand the nodes in the right hand pane to explore the security data.
  • Use the button drop down list from the heading on the right hand pane to change the view mode.
  • Double click on the nodes on either pane to open the window to edit the selected Security Task, Security Role, etc.
  • Click on the Show Resources button to display the actual list of resources for the node (user, role, task, etc.) selected in the right hand pane.


For more information on the Support Debugging Tool and the previous posts, see the links below:

This is just one of the many benefits of the Support Debugging Tool and another reason why many partners now install the tool on all their sites.