Breaking news from around the world
Get the Bing + MSN extension
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
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 TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
When upgrading to Microsoft Dynamics GP 2018 R2, similar to what we have seen with prior versions, there are some new security roles and tasks that have been added with the Microsoft Dynamics GP 2018 R2 release and due to this, if you're upgrading to this version whether coming from Microsoft Dynamics GP 2018, Microsoft Dynamics GP 2016/R2, or Microsoft Dynamics GP 2015/R2, you will need to run the attached scripts to make sure all of the security records are present in Microsoft Dynamics GP 2018 R2.
The tables impacted are the SY10600, SY10700, SY10800, SY09000 and SY09100 security tables and the new security records are mainly for a Workflow report and some other additions.
You will want to run these scripts against your DYNAMICS/system database for Microsoft Dynamics GP 2018 R2 after the upgrade has been completed on all databases and backups of the databases have been completed.
This is by design in that we do not roll down new security roles to an existing Microsoft Dynamics GP environment, which could potentially cause issues with your current security design. Therefore, we have chosen to release these new security records, along with all security records, as an INSERT script, even though we do not recommend making any modifications to our default security roles or security tasks, but instead create custom security roles and security tasks to use and make changes to.
A new installation of Microsoft Dynamics GP 2018 R2 databases will already have all of these security records in the tables, it is only when upgrading from a prior version to Microsoft Dynamics GP 2018 R2 that this issue will occur and require the running of these security record scripts to add to what exists already in these tables.
The scripts for Microsoft Dynamics GP 2018 R2 security roles and security tasks can be downloaded from the following link:
SECURITY RECORDS FOR MICROSOFT DYNAMICS GP 2018 R2_Updated.txt
***NOTE: When you run these insert scripts against your system database for Microsoft Dynamics GP 2018 R2, it is normal that you will see some PRIMARY KEY error messages referencing duplicate records trying to be inserted into the security tables. This can be ignored as it means that the record(s) already exist in these tables. That being said, make sure to have a valid backup of the DYNAMICS/system database before running these INSERT scripts against it.
Good Luck Upgrading and Enjoy Microsoft Dynamics GP 2018 R2!!!
Derek, there is an issue with 2018R2 new function REASON CODES. The reason codes window is incorrectly placed in system, it should be in inventory I believe, I spent a lot of time trying to find in inventory. Also, it looks like the script to add new security doesn't add this one, and also does not add to security resource descriptions.
We are on GP 2018 R2 18.628 and worked the first time, no issues to report.
RE Eric Jackson's comment - we experienced the same exact situation affecting various Windows and Reports for the DEFAULTUSER.
Running this script against my customer's GP 2018 R2 broke the Default User ID in Alternate Modified Forms and Reports. It has unselected some of the windows and reports, like Vendor Maintenance. I just ran the script on my test 2018 R2 and it broke that as well. I had to open the DEFALUTUSER and manually select some of the radio buttons. The ones it broke just had nothing selected.
Business Applications communities