Connector -- Integrating Dynamics ERP with Dynamics CRM

Connector for Microsoft Dynamics is an integration solution which is targeted specifically at the Microsoft Dynamics product family. Connector provides an out of the box integration between Dynamics CRM and Dynamics ERP solutions.

Connector for Microsoft Dynamics V3 CU 2 Released

Connector for Microsoft Dynamics V3 CU 2 Released

Rate This
  • Comments 30

Performance improvements and key suggestions on Connector V3 deployments are the primary new features in Connector for Microsoft Dynamics V3 CU2 (3.2.606.2), which was posted Monday for download.

Additional new features with this release include:

  • Web-based viewer for the Connector's log
    • To access the log via the web-based viewer, you will need to be receiving notifications of the exceptions in the system and click on the link in those notification emails
  • Overall performance and messaging improvement in Connector's log
  • Version information has been moved to an "About" box within Connector

To download this release for your Microsoft Dynamics ERP system, go to Customer Source:

  • Connector for Microsoft Dynamics AX
    • If you have applied Microsoft Dynamics AX 2012 R2 CU 6 or later, an XPO is no longer needed.  You can run the ConnectorHelper class that is included in the CU 6 update to accomplish the required setup tasks in Microsoft Dynamics AX 2012 R2.
    • This release is required for integrations targeting the upcoming Microsoft Dynamics AX 2012 R3 release
  • Connector for Microsoft Dynamics GP
    • All previously supported versions of Microsoft Dynamics GP 2010 and GP 2013 are supported as either new or existing integrations
    • The upcoming Microsoft Dynamics GP 2013 R2 release will also be supported with this release, however it is not required for integrations targeting Microsoft Dynamics GP 2013 R2.
  • Connector for Microsoft Dynamics NAV
    • Microsoft Dynamics NAV 2013 R2 is supported with this release, however this release is not required for an integration to Microsoft Dynamics NAV.  Any release after Connector V2 RU1 (2.1.29.1) will support Microsoft Dynamics NAV 2013  R2.
  • Connector for Microsoft Dynamics SL

Would you like to know more?  Check out the User Guide for your ERP system and begin your installation preparation. I know, I know; reading documentation can be arduous. But you know what they say: an ounce of prevention is worth a pound of cure. So read the provided documentation to avoid the common mistakes and save yourself the support call.  The user guides for all of the ERPs have been updated for this release and all include a V3 upgrade sections that you should be familiar with before upgrading your existing integrations.  All of the known issues documents have been updated as well so please have a look at those too, they can all be found on the Connector for Microsoft Dynamics download pages.

Note: This release includes an update to the MSDI database that will mean any custom objects you have added to the database will be dropped, however this update will greatly improve the performance of the overall Connector system.

PLEASE READ BEFORE POSTING
Please only post comments relating to the topic of this page.
If you wish to ask a technical question, please use the link in the Related Links section (scroll up, on right hand side) to ask on the Dynamics Communities. If you ask on the Communities, others in the community can respond and the answers are available for everyone in the future.
Leave a Comment
  • Please add 1 and 1 and type the answer here:
  • Post
  • When trying to install the Integration Solution for Dynamics AX projects and Microsoft Dynamics CRM, I cannot generate the mapping for the new entities (mbs.microsoft.com/.../MSDCRMAXIntegrationSol). I followed the installation guide, however it seems that the exe file is corrupted.

    When getting to the stage of installing the mappings for the new services (Step 5 Page 18 of the installation guide), I cannot access the exe file.

    Has anyone reported this issue?

    Ahmed

    ahmednafea.ahmed@gmail.com

  • Hello Ahmed, Thanks for the feedback, we will look into this.

    Regards,

    Pradeep (Program Manager for the Project-CRM integration solution)

  • @Pradeep GanapathyRaj [MSFT]

    Thanks for your response.

    Regarding the Order to Sales Order Service from CRM to AX 2012 R2 CU7, when submitting the order from CRM 2013 the Sales Order Type is defaulted to "Journal" instead of "Sales Order". I checked my settings  under AR Parameters for default Sales Order type and its set to "Sales Order". Furthermore, the Sales Type mapping between CRM to AX is set to "Sales" as per SalesType enum value in the AOT.

    I tried different options such as Sales Order, Sales, number 3 which is the SalesType EnumValue for Sales or Sales Order. However, no luck.

    Any advice?

    Regards

    Ahmed

  • @Pradeep GanapathyRaj [MSFT]

    Thanks for your response.

    Regarding the Integration Solution for Dynamics AX projects and Microsoft Dynamics CRM:

    I managed to find a blog post that assist with this issue by debugging the exe file (blogs.msdn.com/.../microsoft-dynamics-crm-2013-is-supported-by-connector-for-microsoft-dynamics.aspx) see the comments section by Mirko.

    However, still facing issues with installing the maps. After using VS to debug the exe and go through the steps performed by Mikro, I get a message saying Maps installed successfully as per configuration documentation provided. Though when starting the service and the connector, I could not find the services on the connector GUI.

    I am running AX 2012 R2 CU7, CRM 2013 and latest Connector Version.

    Any advice?

    Ahmed

  • Hi thehetz,

    I could't install the connector V3.2.  I currently have the connector V3.1 installed.

    But we moved the MSDI db to another SQL server instance.  Then was not able to open the connector.

    I asked questions there. blogs.msdn.com/.../moving-the-msdi-database-to-a-new-microsoft-sql-server-instance.aspx

    But didn't work it out.

    So I tried to upgrade the connector to V3.2. First time, the user I used to install the connector was not the db_owner of MSDI db. so I got the error below .

    Product: Connector for Microsoft Dynamics -- DeployDacPac threw an exception: Microsoft.SqlServer.Dac.DacServicesException: Could not deploy package. Error SQL72014: .Net SqlClient Data Provider: Msg 15247, Level 16, State 1, Procedure sp_droprolemember, Line 51 User does not have permission to perform this action. at Microsoft.SqlServer.Dac.DeployOperation.

    Then I set the user to be the db_owner, and re-tried to install.  still got that error, and I found the user lost the db_owner role in the MSDI db.  That's really strange!

    what kind of privileges should the user used to install the connector have?

    Thank you,

    Alan

  • Hello Ahmed and other readers - we have updated the AX projects-CRM Integration solution mbs.microsoft.com/.../MSDCRMAXIntegrationSol. Please try this, thanks!

    Regards, Pradeep

  • @Alan - the user running the Connector install should be in the db creator and security admin roles in SQL server.  Most of the time the user running the MSI is actually a SQL admin which should always work as expected.

  • Ahmed, did you find any solution to Sales Orders being defaulted as "Journal" in AX rather than "Sales Orders"?

    We have tried different values, as you did, but we can't get it to work and this is very crucial in sales order integration.

  • I am facing a critical issue, earlier one of my mapping was working properly  which was in self reference relationship. means it has been created in parent child relationship. for example saleunit which reference with it self, it is growing hierarchy. mumbai=>> maharastra=>>India=>>world. same entity hold the details. and in the above example, mumbai has lookup of maharasta, maharstra has lookup of indaia.

    my problem is now i am not able to creating mapping(only mapping) and it gets close if i try to create means service gets restart. please help me it has stopped my work.

  • @Subhash - have you logged a support incident for this?  Check the object provider configuration files to ensure the "IsParentField" attribute is set properly on the parent references in your child entities.  If you have a working object provider config from a previous version you should try using that as well.

  • @Simon - which version of Connector and AX are you using?

  • Thanks For your reply. i will check and will update.

  • Hi, I Have checked in the object file created for that particular crm 2011 entity, and I found that isParentField was had value "TRUE" and tried to changed to "True"(i know would not make any sense), even i replace it with the the old may which i had as backup with me. but as soon as i try to create mapping means (choosing source and target) at that time it is stuck and ti closed the window. even it stops the connector service.

  • @Subhash - the situation that you describe can occur when the version of the map in the MSDI database holds a different version of the object config file than is on the file system.  Have you logged a support case for this issue?  At this point contacting support would be your best bet for resolving this issue.

  • I am a MS partner implementing Connector for a customer. I have some questions about mapping fields in Connector for AX 2012. Where can I find documentation about extending the default mappings? Where can I get support for this?

    I need to be able to map the ABC field on Customer form to Account Classification filed in CRM 2013.

Page 1 of 2 (30 items) 12