New CrmSdk force us to use .NET v4.6.2

It’s that time of the year when all older organizations are upgraded to the latest version of Dynamics and with that upgrade tons of new issues are produced as usual.

First of all, I have noticed that a lot of async jobs started to fail (not every time) due to 2 errors:

  • System.ServiceModel.CommunicationObjectFaultedException: The communication object,…

Continue Reading Dynamics Ninja’s Article on their blog

New CrmSdk force us to use .NET v4.6.2

Blog Syndicated with Dynamics Ninja’s Permission

More About This Author

Ivan Ficko
Ivan FickoDynamics Ninja
My name is Ivan Ficko and I’m Microsoft Dynamics CRM developer that has 3 years of experience developing various stuff for Microsoft Dynamics CRM and I’m highly focused on trying new things and pushing the limits on the CRM platform.

I’m following the go-do principle in the development and every post on this blog is a product of something that I really missed on the platform and said let’s try to achieve it.

Most of the time I’m trying to make front end things to improve CRM’s performance, but everything that will make CRM a better platform will keep my attention.

Let’s do some CRM magic guys!

Author: Ivan Ficko

My name is Ivan Ficko and I’m Microsoft Dynamics CRM developer that has 3 years of experience developing various stuff for Microsoft Dynamics CRM and I’m highly focused on trying new things and pushing the limits on the CRM platform. I’m following the go-do principle in the development and every post on this blog is a product of something that I really missed on the platform and said let’s try to achieve it. Most of the time I’m trying to make front end things to improve CRM’s performance, but everything that will make CRM a better platform will keep my attention. Let’s do some CRM magic guys!

Share This Post On