Personalized Community is here!
Quickly customize your community to find the content you seek.
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
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All 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 covered what the SalesHQ portal is, and in this post I’m going to go into a little detail as to how it works.
There are five main components to the SalesHQ portal:
As mentioned, the SalesHQ web portal is hosted by ISC Software on Microsoft Azure; organisations using the portal can supply their own URL for user-friendly naming and access to the portal; for example, I could use https://mobilesales.azurecurve.co.uk/ to give a friendly name for accessing SalesHQ.
The implementation of SalesHQ is a task split between ISC Software and either you or the consultant from your Dynamics GP partner; you, or your partner will install the Connector Service, update the Dynamics GP clients and configure SalesHQ while ISC Software will deploy and configure the Azure components including the web portal.
The key advantage of how SalesHQ has been designed, is that it does not require any incoming ports opened on the firewall as all communications between the portal and Dynamics GP, is initiated by the ,em>Connector Service.
Business Applications communities