Security Restrictions for Command Forms
Guys
One recent support request which came from a few friends of mine, is, when they try to login to GP, they get an error message “You do not have security access” and log them out of GP.
I checked with them to see if they have any customizations and they had a customized product which had a few custom menus created for the customization.
These customized menus were created using a Command Form and the mistake they had done is that, they gave the title of the window in the command form as “~Internal~’’. This may look very normal to everyone. But one thing everyone needs to keep in mind is GP is pretty much case sensitive… 
I asked them to change the title from “~Internal~” to “~internal~” and then the application loaded fine, without any security issues.
Let’s analyze this issue in detail here…
When you create a window with the title “~internal~”, this window bye-passes any security checks in GP. Hence the system does not check if the user has access to this specific window, since it is considered as an internal window, which gets loaded, whether the user has access to it (or) not. This title is case sensitive and needs to be in the correct case. Also the window name should be “Dummy” with the Auto Open property set to TRUE.
These kind of windows are generally used for performing application level tasks like creating menus etc. This is the reason why we create a command form and load all the commands into it and set the title of the window to “~internal~”, so that when GP loads, the application does not check for security on this window and allows us to initialize all the commands and create all the menus.
I am sure many of you would be aware of this, but in case you are not aware of this fact, this article should benefit… Happy Reading…
Until next post…
Siva
April 28, 2009
· 
veeyeskay · 
One Comment
Posted in: Dynamics, Great Plains, System Total Views: 476
Pingback: Around the Blogsphere - Developing for Dynamics GP