Connector -- Integrating Dynamics ERP with Dynamics CRM https://docs.microsoft.com/archive/blogs/dynamicsconnector/feed.xml 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. Tue, 16 Apr 2019 05:05:50 GMT en-US hourly 1 Connector for Microsoft Dynamics support for Microsoft Dynamics CRM beyond Dynamics CRM version 2016 https://docs.microsoft.com/archive/blogs/dynamicsconnector/connector-for-microsoft-dynamics-support-for-microsoft-dynamics-crm-beyond-dynamics-crm-version-2016 Fri, 08 Apr 2016 13:38:58 GMT https://blogs.msdn.microsoft.com/dynamicsconnector/?p=1133 post, the most recent version of Connector for Microsoft Dynamics  (3.4.304.1) (“Connector”) supports Dynamics CRM 2016 (8.x.x.x) both on-premises and online. Today (April 8th, 2016) we are announcing that Dynamics CRM version 2016 will be the last major version of Dynamics CRM to be supported by Connector.

Support matrices for Connector for Microsoft Dynamics as of 10/09/2018

If your Dynamics product version does not appear in these matrices, then it is not supported by Connector for Microsoft Dynamics.

Dynamics NAV support matrix

CRM 2013 6.x.x.x CRM 2015 7.x.x.x CRM 2016 8.x.x.x
NAV 2015 Y Y Y
NAV 2016 * Y Y Y
* Connections to Dynamics CRM using this version of Dynamics NAV should transition to the Dynamics CRM interoperability framework included in the Dynamics NAV 2016 release.

Dynamics AX support matrix

CRM 2013 6.x.x.x CRM 2015 7.x.x.x CRM 2016 8.x.x.x
AX 2012 R3 Y Y Y

 Dynamics GP support matrix

CRM 2013 6.x.x.x CRM 2015 7.x.x.x CRM 2016 8.x.x.x
GP 2015 Y Y Y
GP 2015 R2 Y Y Y
GP 2016 Y Y Y

 Dynamics SL support matrix

CRM 2013 6.x.x.x CRM 2015 7.x.x.x CRM 2016 8.x.x.x
SL 2011 SP1 Y Y Y
  Note: Mainstream support for Dynamics CRM 2011 ended on 7/12/2016 as did official Connector support for interoperability with Dynamics CRM 2011.  The official Microsoft support lifecycle website can be found here.

What does this mean for my current and future Connector implementations?

  • Microsoft Dynamics NAV

    • Dynamics NAV 2016 includes a new interoperability framework for connecting with Dynamics CRM 2015 (7.x.x.x) and successor versions.  We recommend existing Dynamics NAV connections to Dynamics CRM versions greater than 2015 transition to this new framework once the Dynamics NAV instance is updated to Dynamics NAV 2016 or beyond.  New implementations of Dynamics NAV 2016 or beyond and Dynamics CRM 2015 or beyond should use the new NAV framework as well.  More information on this technology can be found at the following link: https://msdn.microsoft.com/en-us/library/dn951570(v=nav.90).aspx
    • Versions of Dynamics NAV earlier than 2016 that use Connector to interoperate with Dynamics CRM versions earlier than 2016 will continue to be supported by Connector  through the life cycle of the Dynamics NAV version.  If the Dynamics CRM instance must be upgraded, we recommend upgrading the version of Dynamics NAV to 2016 or a later version.

  • Microsoft Dynamics AX

    • Dynamics AX versions released after Dynamics AX 2012 R3 will include a new interoperability framework for connecting with Dynamics CRM 2016 and successor versions.  Stay tuned to the Dynamics AX release announcements for more information on that technology.
    • Versions of Dynamics AX earlier than 2012 R3 that use Connector to interoperate with Dynamics CRM versions earlier than 2016 will continue to be supported by Connector through the support life cycle of the Dynamics AX version. If the Dynamics CRM version is upgraded to a post 2016 version, then the Connector implementation will fall outside of the support matrix.  If the Dynamics CRM instance must be upgraded, we recommend upgrading the version of Dynamics AX to a version later than 2012 R3.

  • Microsoft Dynamics GP

    • Dynamics GP will continue to be supported according to the support lifecycle for the given version of Dynamics GP that interoperates with Dynamics CRM until the version of Dynamics CRM is upgraded to a version greater than 2016.

  • Microsoft Dynamics SL

    • Dynamics SL will continue to be supported according to the support lifecycle for the given version of Dynamics SL interoperates with Dynamics CRM until the version of Dynamics CRM is upgraded to a version greater than 2016.
 ]]> Connector download links https://docs.microsoft.com/archive/blogs/dynamicsconnector/connector-download-links Wed, 09 Mar 2016 19:06:47 GMT https://blogs.msdn.microsoft.com/dynamicsconnector/?p=1121 https://blogs.msdn.microsoft.com/dynamicsconnector/?p=1111]]> Connector for Microsoft Dynamics support for Microsoft Dynamics CRM 2016 https://docs.microsoft.com/archive/blogs/dynamicsconnector/connector-for-microsoft-dynamics-support-for-microsoft-dynamics-crm-2016 Mon, 30 Nov 2015 10:29:00 GMT https://blogs.msdn.microsoft.com/dynamicsconnector/2015/11/30/connector-for-microsoft-dynamics-support-for-microsoft-dynamics-crm-2016/ Microsoft Dynamics CRM 2016 has officially released: https://community.dynamics.com/b/msftdynamicsblog/archive/2015/11/30/microsoft-dynamics-crm-2016-now-available-ushering-in-a-new-era-of-intelligent-customer-engagement

The most current version (3.4.304.1) of Connector for Microsoft Dynamics does support Dynamics CRM 2016 in both on-premises and online deployments. More information on this version of Connector can be found in this post: blogs.msdn.com/b/dynamicsconnector/archive/2014/12/04/connector-for-microsoft-dynamics-v3-cu-4-released.aspx

]]> Instance Adapter for Microsoft Dynamics CRM is now on GitHub as open source https://docs.microsoft.com/archive/blogs/dynamicsconnector/instance-adapter-for-microsoft-dynamics-crm-is-now-on-github-as-open-source Tue, 03 Nov 2015 11:42:00 GMT https://blogs.msdn.microsoft.com/dynamicsconnector/2015/11/03/instance-adapter-for-microsoft-dynamics-crm-is-now-on-github-as-open-source/ Today the Instance Adapter for Microsoft Dynamics CRM was published on GitHub as a public open source project using the MIT license.  The current release listed there is a pre-release version for folks to test out and start contributing to if they would like to.  The wiki on the GitHub site has the installation and configuration steps for the instance adapter listed as well.

The current version has not been changed from the previous version that was available last year.

microsoft.github.io/Instance-Adapter-for-Microsoft-Dynamics-CRM

It should be noted that this adapter IS NOT supported by Microsoft support.  This is a community-based project and as such, it is supported via the developer community at the above GiHub site.

 

]]> Microsoft Dynamics AX 2012 R3 Exchange rates not syncing properly https://docs.microsoft.com/archive/blogs/dynamicsconnector/microsoft-dynamics-ax-2012-r3-exchange-rates-not-syncing-properly Wed, 15 Apr 2015 15:14:43 GMT https://blogs.msdn.microsoft.com/dynamicsconnector/2015/04/15/microsoft-dynamics-ax-2012-r3-exchange-rates-not-syncing-properly/ If you are troubleshooting why the exchange rates from Dynamics AX 2012 R3 are not syncing properly into Microsoft Dynamics CRM using Connector for Microsoft Dynamics, here is something for you to take a look at.

In Dynamics AX 2012 the query that is used by the Connector's AX 2012 adapter to retrieve the exchange rates from within Dynamics AX may need to be updated as follows:

  1. De-activate the AX Exchange Rate to Currency map in Connector
  2. Open the Dynamics AX 2012 client
  3. Press CTRL + D to open the AOT
  4. Expand the Queries node and find the AxdConnExchRate query
  5. Expand all of that query's data sources
  6. On the Ledger data source, expand the Relations node
  7. Select the Second relation, and view its properties
  8. Change the Field property to be FromCurrencyCode, instead of ToCurrencyCode
  9. Save a compile the query
  10. Reset the 'Check for data modified after date' to be a date prior to the exchange rates' effective dates and active the map
  11. Click Save within Connector
 
]]> Preserving leading zeroes in numerical constant value mappings https://docs.microsoft.com/archive/blogs/dynamicsconnector/preserving-leading-zeroes-in-numerical-constant-value-mappings Wed, 25 Mar 2015 07:33:34 GMT https://blogs.msdn.microsoft.com/dynamicsconnector/2015/03/25/preserving-leading-zeroes-in-numerical-constant-value-mappings/ If you need to map a numerical value to a constant value and that constant value has leading zeroes, those zeroes will be parsed off.  For example, if want to map a numerical field to a constant value of 00000000115 and you enter a constant value in the mapping wizard, the transformation logic will truncate the leading zeroes.  This results in a constant value of 115 instead of the desired value.  There is a workaround for this behavior using the ReplaceAll() function.

For example you can map the numerical field as follows: =ReplaceAll(ABC0000000115, ABC, "").  This will result in a string being returned from the function: "0000000115".  When the transformation converts this string into a number, it will then preserve the leading zeroes.

]]> Two new Microsoft Dynamics GP case studies have been published https://docs.microsoft.com/archive/blogs/dynamicsconnector/two-new-microsoft-dynamics-gp-case-studies-have-been-published Tue, 17 Mar 2015 13:54:25 GMT https://blogs.msdn.microsoft.com/dynamicsconnector/2015/03/17/two-new-microsoft-dynamics-gp-case-studies-have-been-published/ Two new Microsoft Dynamics case studies have been published on the Microsoft Case studies web site.  They both are Microsoft Dynamics GP customers who are using Connector for Microsoft Dynamics to integrate with Microsoft Dynamics CRM online.

City Harvest Microsoft Dynamics case study

GEARYS Microsoft Dynamics Case study

There is a new list on the left hand side of the blog containing links to our case studies as well.

]]> Mapping the full product name from Microsoft Dynamics AX to Microsoft Dynamics CRM https://docs.microsoft.com/archive/blogs/dynamicsconnector/mapping-the-full-product-name-from-microsoft-dynamics-ax-to-microsoft-dynamics-crm Mon, 23 Feb 2015 08:27:00 GMT https://blogs.msdn.microsoft.com/dynamicsconnector/2015/02/23/mapping-the-full-product-name-from-microsoft-dynamics-ax-to-microsoft-dynamics-crm/ A new post has been authored on the Dynamics AX support blog on mapping the full product name from Dynamics AX into Dynamics CRM using Connector for Microsoft Dynamics.

The description of the post is as follows:

This blog post comes from a question in the Microsoft Dynamics AX community board at https://community.dynamics.com/ax/f/33/t/120425.aspx. The question was how to map the full Product Name and not the NameAlias field that is in the InventTable table. The NameAlias field is a shorter field so it does not give you as good as description. I had originally suggested to use a custom function and provided a sample for it. This custom function would call a new AIF service in AX that would pull the product name.

The full post can be viewed here: blogs.msdn.com/b/axsupport/archive/2015/02/22/map-the-full-product-name-from-dynamics-ax-for-the-crm-connector.aspx

 

 

]]> Hotfix released for Microsoft Dynamics AX 2012 R3 that will allow changes to person name and sales order lines to be tracked with SQL change tracking https://docs.microsoft.com/archive/blogs/dynamicsconnector/hotfix-released-for-microsoft-dynamics-ax-2012-r3-that-will-allow-changes-to-person-name-and-sales-order-lines-to-be-tracked-with-sql-change-tracking Wed, 14 Jan 2015 08:21:49 GMT https://blogs.msdn.microsoft.com/dynamicsconnector/2015/01/14/hotfix-released-for-microsoft-dynamics-ax-2012-r3-that-will-allow-changes-to-person-name-and-sales-order-lines-to-be-tracked-with-sql-change-tracking/ A hotfix has been released for Dynamics AX 2012 R3 that resolves the issue of changes to customer or contact names not forcing a synchronization to occur within Connector for Microsoft Dynamics.  This hotfix will also now allow changes to sales order lines to be tracked and force an update to occur within Connector.  The hotfix can be found in the Life Cycle Services tool using the following link:

https://fix.lcs.dynamics.com/Issue/Resolved/637045?kb=3026356&bugId=3216334&qc=6eac416111d73ae5569bab364b97ef52

The associated Dynamics AX 2012 R3 KB is 3026356.

After applying the hotfix you will need to compile the ConnectorHelper class and then run that class again.

This hotfix only applies to Microsoft Dynamics AX 2012 R3.

]]> Connector for Microsoft Dynamics configuration settings that can be used to control some of the default behaviors for logging and retries https://docs.microsoft.com/archive/blogs/dynamicsconnector/connector-for-microsoft-dynamics-configuration-settings-that-can-be-used-to-control-some-of-the-default-behaviors-for-logging-and-retries Tue, 13 Jan 2015 07:30:00 GMT https://blogs.msdn.microsoft.com/dynamicsconnector/2015/01/13/connector-for-microsoft-dynamics-configuration-settings-that-can-be-used-to-control-some-of-the-default-behaviors-for-logging-and-retries/ There are some configuration settings that can be added or changed in the ConnectorServiceHost.exe.config to update default behavior with respect to retries and log cleanup; they are as follows: 

Config Setting

Behavior

Remarks 

HousekeepingCleanupLogs

True: The Housekeeping task should run CleanupLog.proc.sql and CleanupRetryTask.proc.sql

False: The Housekeeping task will run only run CleanupTaskDeletionTracking.proc.sql (not recommended)

Caution: Log entries and expired Retries can degrade overall system performance if this setting is False

HousekeepingStartTime

The time of day the housekeeping task should run, default is DateTime.UtcNow() or service start time

It may make sense to set this to a time of day that has less load, such as a time after normal business hours

Connector uses the DateTime.TryParse() method to parse this setting, see this article for the proper string format.

msdn.microsoft.com/en-us/library/ch92fbc1(v=vs.110).aspx

If the setting can't be parsed then the default of DateTime.UtcNow() is used for this setting

HousekeepingRunImmediately

True: Housekeeping should run immediately upon service start (Default)

False: Housekeeping task should wait until next scheduled run time after service start

 

HousekeepingExpireDayOffset

First usage: Number of days to keep retries that have completed successfully (Default = 3 days)

Second usage: Number * 2 = days to keep retries that were stopped by the user or ran out of retry attempts (Default = 3 *2 = 6)

Making this value smaller gives you less time to restart failed records; making it larger will give you more time to see the log.

Be aware that Making this number too large can affect performance as retries that have run out of attempts over time can degrade overall system performance

 Task Scheduling configuration settings:

ConcurrentRetryTaskLimit

Number of concurrent Retries the system will queue

Also number of connections to Microsoft Dynamics CRM that could potentially be created at any given time

MaximumRetries

Maximum attempts a given retry will make before stopping and waiting for the user interaction to resolve the issue

 

RetryInterval

Number of seconds from initial attempt to first and second retry attempts, Default = 5

RetryInterval ^ CurrentRetryAttempt

5 to 5^MaximumRetries

 

 

]]>