Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
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
This post is part of a series on Implementing SalesHQ Portal, which is one of the GP Elementz Portals from my new employer, ISC Software Solutions.
In the last post in this series, I installed the Connector Service; as part of the installation a database was created and populated with the required tables. The service account is granted access to these tables, but also needs to be granted the DYNGRP role in the Microsoft Dynamics GP system and company databases as well.
You can do this via SQL Server Management Studio. Expand Security and Logins, find the service account, right-click and select Properties.
Select User Mapping and the the system database (which in my example is called D18R2.
In the Database role membership… section, mark the checkbox next to DYNGRP:
Repeat this action for the company databases and then click OK to commit the changes.
This action is only required to be done for the Domain account which will run the connector service as this service handles all connections to the database, including those from the Dynamics GP client.
Business Applications communities