Configuring Microsoft Dynamics AX 2012 for use with Connector for Microsoft Dynamics

This video demonstrates the steps for configuring Microsoft Dynamics AX 2012 for use with Connector for Microsoft Dynamics.  It covers the importation of the Connector for Microsoft Dynamics XPO, handling a code merge, running the setup class and entering the Microsoft Dynamics AX 2012 adapter settings.  It also demonstrates were to go within Microsoft Dynamics AX 2012 to find out more details about exceptions that might be occurring in the AIF services. 


Key take aways from this video include:

  • Importing the DynamicsConnector.xpo
  • The process for preforming a code merge within Microsoft Dynamics AX 2012
  • Running the Dynamics Connector setup class within Microsoft Dynamics AX 2012
  • Viewing exceptions in the Microsoft Dynamics AIF exception log
  • Supplying the proper settings for the Microsoft Dynamics AX 2012 and Microsoft Dynamics CRM 2011 adapters
  • Creating a new integration
Comments (6)

  1. Chris Turner says:

    At 10:16 in the video the Refresh Services button is clicked.  When I click this button I receive a message stating "Unable to connect".  This even happens when that admin is logged in.  Does anyone have any ideas as to why this is?  Any help would be much appreciated.

  2. thehetz says:

    @Chris – this can happen for a few reasons.  The first is that the user that you are currently running as does not have access to the AX metadata service.  The second is that you have a configuration issue wiht those Ax services.  One of the more common issues that we have seen is having the Azure AppFabric installed on the same machien that the Ax AIF services aare installed on.  Removing the Azure AppFabric normally fixes this situation.  You might also try posting this in the Dynamcis Communities which are linked to from the Related Links section on this blog.

  3. Daws says:

    What if something goes wrong and we have to re-instate CRM to how it was before integration. I mean removing the customization added by the connector. Do we have any way to do it ?

  4. thehetz says:

    @Daws – you can remove the solution as you would any other Dynamics CRM solution.  The Configuration utility also writes a log file that can be used as a guide for what other changes are made during configuration so that you can "undo" those changes by hand.  The Installation guide also lists out the changes that are made by the utility.

  5. Jeff green says:

    Why do we have to create separate integration user account for CRM. I have domain account as an administrator. This user is Admin in both products i.e. AX and CRM. Now when I am entering this user credentials in adapter setting for CRM, it is giving me error that, use different account for Integration account (credentials in the first screen of adapter for CRM). Please guide.

    1. thehetz says:

      Because the integration account in CRM is special. Whichever account you specify as the integration account in CRM (if it is CRM online) will be set to non-interactive mode. This means that account can no longer log into CRM from a browser. So if you specify the Admin account here, then your admin will no longer be able to log into the product. Please see the installation guide for more details on these accounts.

Skip to main content