{"id":1796,"date":"2015-10-05T18:08:09","date_gmt":"2015-10-05T12:38:09","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=1796"},"modified":"2015-10-05T18:08:09","modified_gmt":"2015-10-05T12:38:09","slug":"make-cross-domain-web-service-request-through-client-side-scripting-in-dynamics-crm","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2015\/10\/make-cross-domain-web-service-request-through-client-side-scripting-in-dynamics-crm\/","title":{"rendered":"Make Cross Domain Web Service Request through Client Side Scripting in Dynamics CRM"},"content":{"rendered":"

To perform CRUD operations with CRM data at client side we use ODATA and SOAP services of Microsoft Dynamics CRM. We use XMLHttpRequest to send request to these services to get the response.<\/p>\n

Microsoft Dynamics CRM provides below WCF services that we used to manipulate CRM data,<\/p>\n

Organization Data Service \u2013 Protocol:\u00a0 OData (REST)<\/p>\n

http:\/\/<server>\/XRMServices\/2011\/OrganizationData.svc\/<\/p>\n

Organization Service – Protocol: SOAP<\/p>\n

http:\/\/<server> \/XRMServices\/2011\/Organization.svc<\/p>\n

The request to above WCF services from JavaScript code works because these services are in same domain as the CRM server.<\/p>\n

But sometimes we may need to create our own service which accepts data from CRM and sends response back to it at client side and which is hosted on different domain than CRM domain. If we try to call such web service we get an error as \u201c<\/em>No ‘Access-Control-Allow-Origin’ header is present on the requested resource<\/em>\u201d<\/em>.<\/p>\n

This blog will illustrate how to get the response correctly from the WCF service that are hosted on different domain than the domain of MS Dynamics CRM.<\/p>\n

For example, at client side using scripting we need to send name of City of account record to WCF service (.svc) (which is hosted on different domain than CRM) to get respective code for that city.<\/p>\n

The request to service which is not in same domain as of CRM it\u2019s called Cross Domain access\/request.<\/p>\n

If we do XMLHttpRequest to different domain than our CRM or Page is on, the browser blocks this request for security reasons.<\/p>\n

There are ways to rid of this situation. The JSONP method is use to make cross domain request. We can send CROSS DOMAIN AJAX request using JSONP.<\/p>\n

Below is the code snippet that sends cross domain AJAX request,<\/p>\n

$.ajax({<\/p>\n

url: “http:\/\/ad4:51643\/WCFService\/Services\/ProcessData.svc\/GetCode”,<\/p>\n

dataType: “jsonp”, \/\/set data type as jsonp for cross domain request<\/p>\n

contentType: “application\/json; charset=utf-8”,<\/p>\n

data: “city=Florida”, \/\/pass value for city parameter<\/p>\n

success: function (data) {<\/p>\n

alert(“Name:” + data);<\/p>\n

},<\/p>\n

error: function (data) {<\/p>\n

if (data.responseText != “done”) {<\/p>\n

alert(“ERROR: ” + data.responseText);<\/p>\n

}<\/p>\n

else {<\/p>\n

alert(_msgSendRequest);<\/p>\n

}<\/p>\n

}<\/p>\n

});<\/p>\n

Below is the code snippet of WCF service (.svc) function that accept string city and send response in JSON format,<\/p>\n

\/\/Data Contract part of WCF service<\/p>\n[DataContract]\n

public class Company<\/p>\n

{<\/p>\n[DataMember]\n

public string CityCode;<\/p>\n

}<\/p>\n

\/\/Service Contract and OperationContract part of WCF service<\/p>\n[ServiceContract(Namespace = “JsonpAjaxService”)]\n[AspNetCompatibilityRequirements(RequirementsMode = AspNetCompatibilityRequirementsMode.Allowed)]\n

public class ProcessData<\/p>\n

{<\/p>\n

\/\/ To use HTTP GET, add [WebGet] attribute. (Default ResponseFormat is WebMessageFormat.Json)<\/p>\n

\/\/ To create an operation that returns XML,<\/p>\n

\/\/\u00a0\u00a0\u00a0\u00a0 add [WebGet(ResponseFormat=WebMessageFormat.Xml)],<\/p>\n

\/\/\u00a0\u00a0\u00a0\u00a0 and include the following line in the operation body:<\/p>\n

\/\/\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 WebOperationContext.Current.OutgoingResponse.ContentType = “text\/xml”;<\/p>\n[OperationContract]\n[WebGet(ResponseFormat = WebMessageFormat.Json, BodyStyle = WebMessageBodyStyle.Bare)]\n

 <\/p>\n

public void GetCode(string callback, string city)<\/p>\n

{<\/p>\n

Dictionary<string, string> cityCodes = new Dictionary<string, string>();<\/p>\n

cityCodes.Add(“Florida”, “FL”);<\/p>\n

cityCodes.Add(“New York”, “NY”);<\/p>\n

StringBuilder sb = new StringBuilder();<\/p>\n

System.Web.Script.Serialization.JavaScriptSerializer s = new System.Web.Script.Serialization.JavaScriptSerializer();<\/p>\n

Company p = new Company() { CityCode = cityCodes[city] };<\/p>\n

string json = s.Serialize(p);<\/p>\n

sb.Append(callback + “(“);<\/p>\n

sb.Append(json);<\/p>\n

sb.Append(“);”);<\/p>\n

System.Web.HttpContext.Current.Response.Clear();<\/p>\n

System.Web.HttpContext.Current.Response.ContentType = “application\/json”;<\/p>\n

System.Web.HttpContext.Current.Response.Write(sb.ToString());<\/p>\n

}<\/p>\n

\/\/ Add more operations here and mark them with [OperationContract]\n

}<\/p>\n

\/\/web.config file of WCF service<\/p>\n

<configuration><\/p>\n

<system.serviceModel><\/p>\n

<behaviors><\/p>\n

<serviceBehaviors><\/p>\n

<behavior name=”ProcessDataAspNetAjaxBehavior” ><\/p>\n

<!– Add the following element to your service behavior configuration. –><\/p>\n

<serviceMetadata httpGetEnabled=”true” \/><\/p>\n

<\/behavior><\/p>\n

<\/serviceBehaviors><\/p>\n

<endpointBehaviors><\/p>\n

<behavior name=”ProcessDataAspNetAjaxBehavior”><\/p>\n

<webHttp \/><\/p>\n

<\/behavior><\/p>\n

<\/endpointBehaviors><\/p>\n

<\/behaviors><\/p>\n

<serviceHostingEnvironment aspNetCompatibilityEnabled=”true”<\/p>\n

multipleSiteBindingsEnabled=”true” \/><\/p>\n

<standardEndpoints><\/p>\n

<webScriptEndpoint><\/p>\n

<standardEndpoint crossDomainScriptAccessEnabled=”true”><\/standardEndpoint><\/p>\n

<\/webScriptEndpoint><\/p>\n

<\/standardEndpoints><\/p>\n

<services><\/p>\n

<service name=”ProcessData” behaviorConfiguration=”ProcessDataAspNetAjaxBehavior”><\/p>\n

<endpoint address=”” behaviorConfiguration=”ProcessDataAspNetAjaxBehavior”<\/p>\n

binding=”webHttpBinding” contract=”ProcessData” \/><\/p>\n

<\/service><\/p>\n

<\/services><\/p>\n

<\/system.serviceModel><\/configuration><\/p>\n

Important points to make a successful cross domain request,<\/p>\n