The good news is that we haven't found any additional security roles or tasks records that are missing when upgrading to Microsoft Dynamics GP 2016 R2 then what we have seen in the past when upgrading to Microsoft Dynamics GP 2016!!!!
That being said, if you are upgrading from Microsoft Dynamics GP 2013 or Microsoft Dynamics GP 2015 to the new Microsoft Dynamics GP 2016 R2, there will be missing security role and task records, especially in regards to the new functionality in Microsoft Dynamics GP 2016, so the script attached below will need to be run against your DYNAMICS/system database, after making a backup, to verify that all of the security records are present in your SY10600, SY10700, SY09000 an SY09100 security tables.
As the Upgrade guide for Microsoft Dynamics GP 2016 R2 mentions, you will want to run these scripts after the upgrade has completed on all databases and a backup of the GP databases have been made.
A new installation of Microsoft Dynamics GP 2016 or Microsoft Dynamics GP 2016 R2 will already have all of these security records in the system tables, it is only when upgrading to these versions from Dynamics GP 2013 or Dynamics GP 2015 that this issue will occur. The reason for this is by design in that we would not roll down new security roles to an existing Microsoft Dynamics GP environment, which may cause issues with your current security design. Therefore, we have chosen to release these new security records as an INSERT script.
These scripts for Microsoft Dynamics GP 2016 / Microsoft Dynamics GP 2016 R2 missing security roles and security tasks records can be found here, and needs to be run against your DYNAMICS/security database:
This set of scripts includes the security scripts for Microsoft Dynamics GP 2013 R2, Microsoft Dynamics GP 2015, Microsoft Dynamics GP 2015 R2 from prior blogs, as well as Microsoft Dynamics GP 2016. 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/R2.
**NOTE: Because we've combined the INSERT scripts from the other blogs to be included in this one, you may see PRIMARY KEY errors referencing duplicated records trying to be inserted into the security tables. This can be ignored as it means that the record already exists in that table and the script will not overwrite anything that is already present.
Thank you and Happy Upgrading!!!