![]() I wanted to see the window in Microsoft Dynamics GP dictionary which is of resource ID 1452. I was always thinking about something in Smartlist (which is, without any doubt), but system was checking something else in a different dictionary altogether. When user tried to open Custom Reminder window, system checked this table and see whether this user has got access to a window whose resource ID is 1452 in dictionary 0 (which is nothing but product Microsoft Dynamics GP) inside company ID 1 (which is my production GP company). This table is simply called User Security. Which means, I must focus my troubleshooting efforts on this table DYNAMICS.SY10000. Then, how? How would I give access to this window?Īfter around an hour or so, with several script logs and profilers misleading me, I found one interesting statement on SQL Profiler trace, that was executed when the user tried opening that window:Įxactly after this SQL statement, the above error message was thrown at the user. It is a part of Smartlist dictionary.īut trick here is, you cannot see this window listed on when you try to assign this window a particular Security Task using Security Task Setup window. ![]() Ideally, you would think that this window is a part of Microsoft Dynamics GP dictionary. He received an error message as follows:īasically, below is the window which user is trying to open: However in this case we take the output build location for the binary output $(BinDir) and use that folder as the basis for the script to run against.I was reported with a very vague issue: user could not create a custom reminder from a smartlist. ![]() Click the little arrow boxes to the right to see the options available, useful for future reference. The external tools window provides some super handy environment variables you can insert into the fields. The Menu calls the power shell interpreter (Powershell.exe), passing the script to run and the build directory to run the script against as command arguments. The "Deploy GP Addin Locally" menu option should now exist on the Tools Menu of Visual Studio but it wont work yet, not without creating the power shell script it calls. ExecutionPolicy RemoteSigned -File "$(SolutionDir)\Deployment Batch Files\DeployGPLocally.ps1" -BuildOutputFolder $(BinDir)Ĭlick Apply and OK on the window to preserve your changes. Use the “Add” Button on the form to create a new entry with the following value: Visual Studio lets you add custom Tools to the Tools menu, select “Tools>External Tools…”, to set this up. This solution copies the debug files into the application Addins folder if the build is debug, and removes them if it isn’t.įollow this guide for what to do, the following screen shot shows the “Deploy GP Addin Locally” option we are aiming to build… Create the Menu Item in Visual Studio This means I can simply use a hot key to deploy my code to the application and start debugging within GP or testing. I set my development environment up by creating a Visual Studio Menu item to deploy the current build of my GP Addin. This can be done manually but gets old real quick after many iterations. Often when developing Dynamics GP Addins, you may wish to deploy the current build to your local copy of Dynamics GP, perhaps for testing. I demonstrated this technique in one of the sessions I presented on GP development at the 2016 Tampa GPUG conference, but never got around to writing about it.
0 Comments
Leave a Reply. |