How To Install Connector for Microsoft Dynamics GP – Configure Adapters

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 (Start menu » All Programs » Microsoft Dynamics » Microsoft Dynamics Adapter » Connector for Microsoft Dynamics) where you will be presented, on first run, the Adapter Settings utility which will be on the Activate new adapters page.

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);

I hit the Test Settings button to check if things were OK an got the following error;

Despite the warning message, it did confirm that the settings were connect. To proceed I clicked the Configure Microsoft Dynamics CRM hyperlink to launch the Configuration Utility;

The first step of the Configuration Utility is to define the CRM Organization Setup. The URL will default in from the main page of the Connector for Microsoft Dynamics program but the CRM Organization setup details will need to be entered.

First enter the User Name and Password for a CRM Deployment Administrator, in my case I used the main DOMAIN\Administrator account.

Next click the Get Organizations button to have a list of available organisations to be pulled back. I only have Fabrikam, Inc. defined within CRM at the moment. Select the organisation you wish to configure and the solution (Microsoft Dynamics GP) you’ll be linked to;

Next select the entities which should be configured for integration or, as I am, leave it with the default settings;

On the blank Configuration Status for Organization window, click Configure to proceed;

The window will display progress as each element is processed until the final line confirming the process has completed;

When the Configuration Utility is finished you’ll be returned to the programs main window;

To confirm all is well with the configuration, click the Test Settings button;

Before moving onto configuring the GP adapter, open the Dynamics Security Console (Windows Start menu » All Programs » Administrative Tools » Dynamics Security Console), on the Integration Server or other machines on which the Web Services for Microsoft Dynamics GP Management Tools have been installed, and add the Integration user (DOMAIN\DynamicsConnector in this example) to the Microsoft Dynamics Integration – All Companies and Microsoft Dynamics Integration – Integrated Company roles under the Role Assignments node (Console Root » Microsoft Dynamics Security » Microsoft Dynmaics GP Web Services » Role Assignments);

Once done, return to the Connector for Microsoft Dynamics program and the Adpater Settings window. Select Microsoft Dynamics GP 2010 in the list on the left.

Enter the Domain, User Name for the Integration Account and Password. The Microsoft Dynamics GP Web Service URL also needs to be entered. This will be in the format of http://machine_name:port/Dynamics/GPService/GPService;

Click the Test Settings button to test the configuration;

With that confirmation, the configuration of the GP 2010 and CRM 2011 adapters is complete. I’ll give a run through of creating a new integration in the next post.