Previously with Dynamics CRM 2011 we only had Organization Services that used to help interact with data in CRM system. CRM 2016 has provided us Web API now. Web API is similar to Organization service with few differences that we are going to discuss below.
- Unlike Organization Service which was optimized for use with .NET, Web API can be used with different programming languages.
- Unlike Organization Service, no longer required to use libraries specific to Microsoft Dynamics CRM. Web API is built on open standards.
- Plug-ins or workflow assemblies on the server still expect to use the Organization service.
- Eventually the Web API will replace the Organization service and Organization Data service.
- The Web API should be your first choice for new development that will support Microsoft Dynamics CRM 2016 and future versions of Microsoft Dynamics CRM Online.
- You can use the Web API Discovery service instead of IDiscoveryService web service. The Web API Discovery service provides the same benefits as the Web API. This service enables your applications to determine, at run-time, the organizations that the signed-in user belongs to.
-
There are three different ways to manage authentication when using the Web API.
- JavaScript in web resources: With JavaScript within HTML web resources, form scripts, or ribbon commands you don’t need to include any code for authentication. In each of these cases the user is already authenticated by the application and authentication is managed by the application.
- On-premises deployments: For on-premises deployments, must include the user’s network credentials.
- Microsoft Dynamics CRM Online or internet facing deployments: For CRM Online or an on-premises Internet-facing deployment (IFD), must use OAuth.
- Perform operations using the Web API
- Web API types and operations
- Web API Limitations
crm backlog 