While I was working on the series of posts for how to install the Web Services for Microsoft Dynamics GP, I encountered a couple of problems which I thought it might be worth covering in this and the next post.
The first was to do with the eConnect Integration Service which is installed as part of the install of Web Services. The basic problem was that the service was not running;
With the web services installed, configured and verified we can install the Management Tools on a client machine so we don;t need to access the server each time we need to make a change; note that the Management Tools can only be installed on a client machine if there is a domain controller on the network.
To install the Web Services Management Tools, open the Microsoft Dynamics GP setup utility and select Web Services Management Tools;
Now that the web services are installed and configured it is time to make sure that they have installed correctly. The Microsoft documentation for Web Services Installation and Administration Guide starts by checking the services are running via the browser and I’ll come to this in a moment, but I always prefer to start with making sure the services are actually running.
This is done in the Services window (
The first service to check for is the Microsoft Dynamics GP Service Host. If the service has a Status of Started then the service is running correctly;
Microsoft Dynamics GP 2013 was released on December 19th last year which means that not only do I have a new version of GP itself to install and play with but also lots of related products such as Business Analyser and Integration Manager.
I am also going to be taking a look at some more of the related products, included the new Microsoft Dynamics GP 2013 Web Client, over the coming few weeks/months depending on how spread out they get due to other commitments. I am going to cover the Web Services in this and the next few posts (perhaps allowing for a couple of non-sequitur posts to slip in).
The first step in installing the Microsoft Dynamics GP 2013 Web Services is to install the runtime components which is done in the Microsoft Dynamics GP 2013 setup utility by selected the Web Services Runtime;
The next few posts will cover the installation and configuration of the Web Services for Microsoft Dynamics GP 2013, but, first, I thought it might be useful to give an overview of the prerequisites.
First, the operating system; Windows Server 2008 or Windows Server 2008 R2 Standard or Enterprise editions are supported. According the the documentation, Windows Server 2012 is not yet supported although the install does work.
Second, a Microsoft SQL Server 2008 or later to host the security database. This could be the same or different SQL Server which is hosting the Microsoft Dynamics GP 2013 system and company databases.
Third, Microsoft .NET Framework 4 is required and will be installed by the Microsoft Dynamics GP setup utility.
Fourth, a service user account is needed to run as the Microsoft Dynamics GP Service Host which is the Windows service host. If you’re running web services on the SQL Server then you can use a local user account but if the web services are on a different machine to the SQL Server then a domain user account should be used.
Fifth, the is two bits of setup which needs to have been completed in Microsoft Dynamics GP 2013:
- A Functional Currency needs to be configured in the Multicurrency Setup window (
- All currencies need to have a unique ISO currency code (
The next post will take a look at the installation of the Web Services Runtime
This is the seventh post in the series on how to install the Connector for Microsoft Dynamics GP; the first six posts covered the prerequisites, installation, adapter configuration, creating a new integration, preparing data for integration and synchronise picklists.
Now that the Connector for Microsoft Dynamics has been installed and configured, the data has been prepared for integration and pickilists synchronised, the next step is to start running the integrations.
As an example, I’m going to step through the process of integrating the Unit of Measure Schedules from GP into the CRM Unit Groups.
In the Connector for Microsoft Dynamics (UofM Schedule to Unit Group node ( );
) navigate down to the
This is the sixth post in the series on how to install the Connector for Microsoft Dynamics GP; the first five posts covered the prerequisites, installation, adapter configuration, creating a new integration and preparing data for integration.
One of the things that needs to be done before integrating Microsoft Dynamics GP with Microsoft Dynamics CRM is to synchronise the CRM picklists with data in GP. This can be done using the supplied Microsoft Dynamics CRM Picking Sync utility which is installed along with the Connector for Microsoft Dynamics.
There is no menu item created for this utility, so you will need to open Windows Explorer and navigate to the installation folder (Microsoft.Dynamics.Integration.GpToCrmPicklistSync.exe;
) and double click the
This is the fifth post in the series on how to install the Connector for Microsoft Dynamics GP; the first four posts covered the prerequisites, installation, adapter configuration and creating a new integration.
In this post, I’m going to highlight an issue which bit me when I was creating this series of posts using the Fabrikam, Inc. demo company.
This isn’t an issue I’ve encountered in the wild, so to speak, but it is a difference in how Microsoft Dynamics GP and Microsoft Dynamics CRM handle Unit of Measure Schedules and Unit Groups respectively.
Microsoft Dynamics GP allows for Unit of Measure Schedules to have two UoM details of the same name. For example, the Fabrikam, Inc. Unit of Measure Schedule Wire contains Spool defined as both 100.00 Foot and 33.33 Yard;
This is the fourth post in the series on how to install the Connector for Microsoft Dynamics GP; the first three posts covered the prerequisites, installation and adapter configuration. This one will show the step-by-step process to create a new integration between Microsoft Dynamics GP 2010 and Microsoft Dynamics 2011.
To create a new integration between Microsoft Dynamics GP and Microsoft Dynamics CRM, open the Connector for Microsoft Dynamics from the Windows Start menu (
To create a new integration, click the New Integration button on the toolbar;
This is the third post in the series on how to install the Connector for Microsoft Dynamics GP; the first two posts covered the prerequisites and installation. This one will show the step-by-step process to configure the Microsoft Dynamics GP 2010 and Microsoft Dynamics 2011 adapters.
To configure the adapters, open the Connector for Microsoft Dynamics program (Activate new adapters page.
) where you will be presented, on first run, the Adapter Settings utility which will be on the
Enter the Integration Account (in my case DOMAIN\DynamicsConnector) and password and also the URL for the Microsoft Dynamics CRM Discovery Service.
The account being used for the Integration Account needs to be a valid CRM user with organization level read privileges for SystemUser (I usually do this by creating a role only with this one security privilege) on the organisations you’re going to integrate into. This user will be added to the following security roles by the configuration utility (which I’ll cover in a moment);
- System Customizer
- Dynamics Integration (this security role is automatically created)
The URL for my system is http://azc-crm1:5555/XRMServices/2011/Discovery.svc (your address can be found in Dynamics CRM under Settings >> Customise >> Developer Resources);