Thursday, June 16, 2016

~internal~ Windows have no place in security

Have you ever wanted to use security to disallow the system Setup Checklist? You access this window using the Microsoft Dynamics GP button and then Tools > Setup > Setup Checklist. As it turns out, you cannot turn it off. Any window resource that has the name ~internal~ is not available to the security model. Now, if you hacked the dictionary (NOT recommended and a violation of your license agreement) and changed the object's name, you could then get to it, but that's not a good idea.

I had a bright idea once and thought I could use Modifier to move all of the fields off of the window. That worked fine, except it wasn't available to select in the Alternate/Modified Forms and Reports window (such a catchy name). I read a GPUG forum post from Jeff Martin that said you could include the Setup Checklist window in a VBA project, so I set out to see if I could get it to work with VBA. Sure enough, you can cause the window to open invisibly, but that doesn't really solve the problem. The reason for this post is to publish a tidbit revealed to us by David Musgrave of Winthrop Development. He said that "part of the issue with the checklists window is that the one window is used for all checklists from all series". I did not know that. Another mystery solved. Thank you David.

Live the dream!


Anonymous said...

Nice post Leslie, an interesting one.
After reading it my brain started think what are the possibilities with dexterity to make this window secure. And what I am thinking is that can register trigger for 'Open of form SY_SetupChecklist' and after verifying authentic user or other conditions can reject opening of window through dexterity.

Unknown said...

I'm getting an error in Michigan. Keeps saying to try again later. Must be a bandwidth issue with your provider.

advanced windows tips and tricks