Big Promise: 2011 SOAP Endpoint Silent Retire

December 18, 2017

one comment

I noticed the following note in the developer guide article.


This note embodies big promise for many organizations that are currently planning or actually migrating from version 2011 (and up) to version Dynamics 365, as it removes (or at least dramatically postpones) a big chunk of work required to migrate code that uses the 2011 SOAP endpoint to use Web API endpoint.  In typical enterprise level projects (versions 2011 to Dynamics 365) the 2011 SOAP Endpoint (a.k.a OrganizationService) is heavily used in Plug-ins, Custom Workflow Activity components, external application integration and even client side code.

For organization planning an application re-do (rather than an upgrade) this means an option to re-use existing code investments (e.g. non-changing integration points with external applications).

When considering an upgrade to Microsoft Dynamics 365, code components migration is a primary workload for most organizations. Although it is recommended to use the modern Web API, reducing or eliminating this workload means a whole different time frames and resources requirements for the migration process. 

Add comment
facebook linkedin twitter email

Leave a Reply to Nemath Cancel Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>


one comment

  1. NemathDecember 27, 2017 ב 3:37 PM

    Hi Yaniv,

    I am a big fan of your blogs and I read all your blog posts.
    I need to run a Schema generator tool on CRM 2011 IFD Instance. I normally use XrmToolKit to do this but it is not working. It is giveing an error when making a connection to CRM 2011. Could you please help me how to resolve this issue?
    The error is as below
    Microsoft.Xrm.Tooling.Connector.CrmServiceClient OrganizationWebProxyClient is null
    An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail.
    Error : ID3242: The security token could not be authenticated or authorized.