Hi @Rod Carlson,
The CRM online expose 2 endpoints publicly :
The older one (2011) is SOAP. This is the one used by the SDK
The newer one is Odata. This is the one referenced as "WebApi"You can see in Microsoft documentation(https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/work-with-data-cds) that SDK is the way to go for plugins, and webApi for calls from outside the CRM.Personnaly, I always prefer using the SDK. When used properly, it create clean code, easy to write, read, and debug.Yet, the fact that it use an old endpoint is annoying...
So we are now trying to use WebApi for our new projects.To help using it, we discovered Xrm.Tools.WebApi. It is an odata client library that let us works with CRM entities. It can generate early binding entities from your CRM to help development. This is done trough a plugin in XrmToolBox.Best Regards,
Yet, the fact that it use an old endpoint is annoying...
Hi @Daryl LaBar,
2 or 3 years ago, I have read from Microsoft that the will transfert SDK call to the odata WebApi, that is why I kept using it and was very happy with this.
But this year I read this from Microsoft Documentation :
"Because the Web API is built on open standards, we don't provide assemblies for a specific developer experience"
So this is the status for me :- Microsoft told us several years ago that they will update the SDK, but no news since- Microsoft advise us to use the WebApi- Microsoft tell us that they don't provide assemblies for itI was getting the feeling that the transfer to SDK was not a priority for microsoft and will just never happens!
This is why your information about proof with fiddler that transition has started for some of the call is great news for me! I will definitively try to follow this to!
If you've found this thread useful, dive deeper into User Group community content by role