Try Microsoft Edge
A fast and secure browser that's designed for Windows 10
Similar to past versions, we've discovered that when upgrading from Microsoft Dynamics GP 2013 or Microsoft Dynamics GP 2015 to the new Microsoft Dynamics GP 2016, we're missing security roles and security task records, especially in regards to new functionality in Microsoft Dynamics GP 2016.
The Upgrade Manual for Microsoft Dynamics GP 2016 notes that you will need to run these scripts after upgrading to Microsoft Dynamics GP 2016.
A new installation of Microsoft Dynamics GP 2016 will create the system database will all of these security records, but during an upgrade it is by design that we would not roll down new security roles to an existing Microsoft Dynamics GP environment that may cause issues with your current security design. Therefore, we release the new security records as scripts.
These scripts for Microsoft Dynamics GP 2016 missing security roles and security tasks can be found here, and need to be run against your DYNAMICS/system database:
UPDATED_DYNAMICS GP 2016 SECURITY INSERT SCRIPTS ALL_June17_2016.txt
Update: This set of scripts includes the security scripts for Microsoft Dynamics GP 2013 R2, Microsoft Dynamics GP 2015 and Dynamics GP 2015 R2. You'll need to run this script whether you're upgrading from Microsoft Dynamics GP 2013/R2 or Microsoft Dynamics GP 2015/R2 to Microsoft Dynamics GP 2016 RTM.
**NOTE: Because we've combined the INSERT scripts from the other three blogs to be included in this one, you can expect to see PRIMARY KEY errors referencing duplicated records, which is fine, as that simply means that the record already exists and these scripts will not overwrite those.
Thank you Derek,
I noticed that some of the missing security objects were already missing in GP 2013R2 & 2015, but have only been corrected now with this version of the script for 2016..
The Edit 1099 Transaction Information form had no security assignment at all and was only visible to POWERUSER role..
Can this updated Script be run against a 2013R2 or 2015 instance ? I'm a little worried that there would be security resources not covered or required in those versions..