If you wanted to access your CRM from the javascript using web services, the only option until CRM 2016 was to wrap your script as a webresource. That way script is hosted in the same domain as CRM and “rides” authenticated session of your browser. External pages were no go because of the Cross-Origin Resource Sharing (CORS) issues.
CRM 2016 has CORS enabled so now you can create awesome things like single-page applications (SPA) that securely talk to CRM. I thought of putting some cool code together but, as usual, Jim “That’s Mr SDK for you” Daly was the first off the blocks with an SPA sample for CRM.
The most tedious part is authentication but now it’s an absolute breeze with the release of ADAL for javascript. Kilolines of code are now reduced to (simplified version, of course):
window.config = {
tenant: "contoso.onmicrosoft.com",
clientId: "ef46083a-abba-dead-beef-4aafd81a93f5",
postLogoutRedirectUri:
"http://contoso.com/crmspa.html",
endpoints: { orgUri:
"https://contoso.crm.dynamics.com" },
cacheLocation: 'localStorage',
};
var ac = new AuthenticationContext(config);
ac.login();
ac.acquireToken(config.endpoints.orgUri, talkToCRM);
Detailed documentation is available, of course, from the Jim’s team. If you’re thinking of reusing your old code, that’s a no go, unfortunately, as CORS is only supported for Web API and not SOAP or OData v2.
