In CRM integration projects, there is often a need to track your source data changes in an efficient way. Currently you would typically implement your solution by comparing CRM entity's modifiedon field, which may not provide the desired performance that you require.
In the past, plugin debugging has been a very challenging task when working with CRM online environment. With the introduction of plugin trace logging feature in the CRM Online 2015 Update 1 release, this has become a much easier job.
Microsoft Dynamics CRM uses a number of special fields for special purpose, those fields used to require using special SOAP messages in order to write to them. With CRM online 2015 Update 1 release, you no longer have to make special service calls to update those fields, which makes it significantly easier to write integration code, at the same time it now offers much better performance due to the reduced service calls.
Upsert is another important enhancement that Microsoft Dynamics CRM team brought to CRM 2015 Update 1 release. When utilized properly, it can significantly simplify your data integration development.
In this blog post, I will discuss how you can setup CRM alternate keys and how you can utilize them in your application.
In this blog post series, I will try to illustrate some of the new capabilities that are offered in Microsoft Dynamics CRM Online 2015 Update 1 release.
We have received a few reporting from our customers saying "The connection manager '' is not properly installed on this computer" when using SSDT-BI for Visual Studio 2013, this blog post tries to direct you to the download link which includes a fix for this issue.
We have received a couple of reporting of a new error indicating that the securityTokenResponse parameter is null when trying to establish the connection with CRM server.