Web API in 2016

(0) Share

Report

Posted on by Community Member

We are in beginning phase of an upgrade from a 2011 on premise to 2016.

Our current 2011 environment uses an ASP.Net MVC web-api service whereby calls from javascript on form loads calls this service to determine various data in the CRM environment. For example, it may use it to get data on a related entity record .

Is this kind of setup still viable with 2016. Knowing that 2016 has a web-api functionality now , trying to grasp the differences and whether our current setup could be ported over .

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

Alex Fun Wei Jie 33,628 on at

Like (0)

Report

Hi,

are you using crm 2011 endpoint to run your web service? if yes, this is deprecated.

msdn.microsoft.com/.../dn281891.aspx

community.dynamics.com/.../205882

Was this reply helpful? Yes No
Suggested answer

Michel van den Brink 4,697 on at

Like (0)

Report

Hello,

To better understand your question: Inside of CRM, you are calling an external API? Where is this MVC WebApi sourcing it's data? From any Dynamics Main Form (in any version) you can call a WebApi using JavaScript as you are doing, using the XMLHttpRequest object.

If you're referring to data you are loading via your API, which in turn calls the Dynamics SOAP API (OrganizationService.svc), that last one has been deprecated and you should look to rewriting those calls to the new WebApi endpoint, which will replace the old SOAP API, which already an MVC WebApi, and can also easily be called via JavaScript.

More about the new WebApi:

docs.microsoft.com/.../use-microsoft-dynamics-365-web-api

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

The MVC webapi is on the same server . On the form on load javascript, for example, we might have a call to another javascript file passing in the guid of the CRM record we want to get more info about. That javascript file will call a "caller" javascript file with a controller and action parameters along with the data being passed. This then calls the web-api service url with the controller and action and data parameter needed. The web-api can query CRM data and return back whatever is needed by the original javascript form . We use it for things like finding if a user is part of a particular team etc.

Was this reply helpful? Yes No
Suggested answer

gdas 50,091 Moderator on at

Like (0)

Report

Hi ,

Your API code will may not work with latest SDK of Dynamics CRM 2016. So you can say those will not work properly unless you are fixing the compatibility syntax of latest SDK dll.

Secondly if you are using JQuery ,Ajax post to call WEB API , its should work.

You just need to check the organization service you are using below when you creating proxy in C# code.

[organization url]/XRMServices/2011/OrganizationData.svc

Hope this helps.

Was this reply helpful? Yes No
Suggested answer

Aric Levin - MVP 30,190 Moderator on at

Like (0)

Report

Hi R T,

Per Microsoft:

As of the release of Microsoft Dynamics CRM Online 2016 Update 1 and Microsoft Dynamics CRM 2016 Service Pack 1 (8.1.0), the CRM 2011 endpoint has been deprecated. The 2011 endpoint will be removed some time after the release of Dynamics 365 version 9. We plan to provide updates to the Dynamics 365 SDK assemblies and tools over the next several minor releases, retargeting them to use the Web API instead of the 2011 endpoint.

This means that at this point whatever you have should still work, because although deprecated, it has not yet been removed, but you should consider that a future upgrade to CRM v9.x On Premise, this might not work.

Please check following link for further details:

msdn.microsoft.com/.../dn281891.aspx

Hope this helps.

Was this reply helpful? Yes No