New April Hotfix and more changes for VAT
Check out the latest updates to Microsoft Dynamics GP 2016 and 2018.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants.Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements.
ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
I'm new to VS Tools for Dynamics GP. I developed something simple and added it to the Financial menu. I can see it when I login as sa. Also, users can see it when they are assigned to the POWERUSER role. however, if the user is not assigned to the POWERUSER role, he cannot see it. Which windows or files do I need to give them access to?
The PowerUsers can see whatever this custom object is that you created in VS Tools because these type of users don't really use the security roles/tasks that non-PowerUsers do, meaning, when a non-PowerUser attempts to open a window or report, for example, a call is made to a SY10000 view, which holds all the object records a user is assigned via the roles/tasks assigned to them (reports, windows, posting permissions, etc) and if it finds a record for that window or report's security ID/dictionary ID/company ID/user id, the user is allowed to open the object, otherwise they'd get a permissions error.
From what you mentioned, this sounds like you added a menu option into Dynamics GP but only PowerUsers see the menu? If so, when they click on this menu option, what does it do? I.e. open a window or report?
Thanks for getting back to me on this. Yes, this menu item has several sub-menu items that each opens a different window. I was unable to even find those windows in security anywhere (i.e. to assign them to a task and assign the task to a role then to a user). Is there is something special to give access to Add-in?
Well, assuming you're testing PowerUsers and non-PowerUsers on the exact same Dynamics GP instance and your VST addins have been added to the AddIns folder of that GP instance, the VST code is going to run whether or not the user is a PowerUser or not, it's just whether the user has security access to that object, such as a window.
If you look in the Alternate/Modified Forms and Reports window, do you see these VST windows that you are referring? If so, expand them and do you see an alternate version of the window? I mention this because even though users can be PowerUsers or not, they are also assigned to an alt/mod ID, such as DEFAULTUSER, and it is through this ID that users are given access to modified objects and/or alternate objects.
For example, if you had a BSI version of a window, users may not have access to it until you assign permissions to the alternate version of the window via their alt/mod ID, whether DEFAULTUSER or whatever.
Other than that, you could try a dexsql.log of when a PowerUser access these custom windows to see if you see any calls to the SY10000 view or SY10800 table, which could potentially give us the securityid of the object you would need, along with the dictionary id and secrestype value, to potentially add that object to a custom security task and role.
Business Applications communities