Wednesday, November 19, 2008

Developing for Dynamics GP

 

Developing for Dynamics GP

How to resolve Security Privileges errors

Yesterday, November 18, 2008, 7:30:00 PM | David MusgraveGo to full article

David Meego

From the Microsoft Dynamics GP Application Level Security Series.

When access is denied by the application security system to a window, you will receive the following error message:

You don't have security privileges to open this window. Contact your system administrator for assistance.

Sometimes, the window you expected to open does not, which probably means that the security on that particular window needs to be changed.  Other times the window still opens even after the security error, which probably means that a hidden system window failed to open.

Either way, the error message itself does not provide enough information to be able to identify the resource causing the issue.

Version 8.0 and 9.0 only: If you are using Advanced Security, you can use the interactive dialogs to identify the resource causing the error message:

  1. Click Tools, click Setup, click System, and then click Advanced Security.

  2. In the Advanced Security window, click Options, and then click to select the Allow security override using the system password check box.

  3. The next time that the error occurs, Advanced Security identifies the resource and provides options to change the security settings.

  4. You can disable the option after the security issue is fixed, or you can leave it active.

For all versions: You can use the Support Debugging Tool for Microsoft Dynamics GP and its Security Profiler feature to identify the resource causing the error message. As we are only using Standard Mode features, any user can be used.

Below are the steps, please skip steps already completed previously:

  1. Click here for the links to download the tool from PartnerSource.
  2. Extract the archive files to your application folder.
  3. Launch Microsoft Dynamics GP and select Yes to include new code.
  4. Log into Microsoft Dynamics GP.
  5. From the menus click Microsoft Dynamics GP (for v10.0), click Tools, click Support Debugging Tool.
  6. From the Support Debugging Tool window, click Options, click Security Profiler. Screenshot below:
    Security Profiler
  7. Now perform the actions to generate the security error message.

While the Security Profile window is open all security checks made are recorded and the results and full details of the resources involved are displayed.  The resource(s) causing the error will be shown as Access Denied.

Note for v10.0 only: If the window is a third party hidden window, please contact the developer of the product in question and request that they update their code to remove their hidden window from the security system. The methods involved are described in the Integration Guide manual installed with Dexterity.

For v8.0 & v9.0: You can then use Advanced Security (Tools >> Setup >> System >> Advanced Security) or Standard Security (Tools >> Setup >> System >> Security) to grant access.

For v10.0 or later: You can use Security Tasks and Security Roles to grant access. For information on how to identify the Security Tasks and Security Roles linked to a particular form, please see the How to identify the Security Tasks and Security Roles associated with a specific window or report post or the How to identify the Security Tasks and Security Roles using the Support Debugging Tool post.

If the errors occur during login before the Security Profiler can be used, please see the How to resolve Security errors on Login post.

For more information on security, please look at the following FAQ Knowledge Base (KB) Articles:

Frequently asked questions about Advanced Security and about Field Level Security in Microsoft Dynamics GP and in Microsoft Great Plains (KB 894705) Secure Link

Frequently asked questions about role-based security in Microsoft Dynamics GP 10.0 (KB 951229) Secure Link

David

Developing for Dynamics GP

No comments:

Blog Archive