Any help?

so everyone in the world who uses the webservices runs it locally from the harddrive of the crm server... come on anyone?

Brad

You'll need to start to break this problem into a number of distinct bits.

If you are trying to make web service calls from a web page them you need to consider

1) The usage and execution of the XMLHttpRequest object. Bear in mind that the original article I wrote was in the bad old days of old fashioned Internet Explorer. You'll need to find a good example of a simple XMLHttpRequest that will make a simple resource.

You are making a SOAP request using the XMLHttpRequest object but have a look at this thread

community.sagecrm.com/.../30299.aspx

Although that is about calling a dll it nevertheless looks at breaking the problem down into bit sized pieces.

2) Are you sure that you want to use the SOAP or the SData API?

Tried opening a support ticket, got told its not something they can help with... anyone in the community ello?

Are you directing the SOAP requests to the correct path?

e.g.

localhost/.../SOAP

You will need to make sure that the web services submits to your CRM instance.

SOAP because I need to update the database.

I actually have all of the code working, I just can't run it from anywhere but the local C drive.

I'm using: myservername/.../SOAP

the request is being sent to the correct server. As I said it runs just fine when I run from the C: drive of the server, but if I run it from anywhere else I get an access is denied message. The message is returned My webservice settings has the WSDL avaible to all.

$.ajax({

type: "POST",

url: webMethod,

data: strXML,

contentType: "text/xml; charset=utf-8",

dataType: "xml",

complete: function (xmlHttpRequest, status) {

$(xmlHttpRequest.responseXML)

.find('result')

.each(function(){

SID = $(this).find('sessionid').text();

});

GetPreFillData();

},

error: function (e) {

alert('Something is wrong...');

}

});

I get the same result if I don't use the jquery ajax call and use just xmlhttprequest.

My issue is probably due to same origin policy.. although I thought calling it from localhost wouldn't violate same origin... either way it looks like in order to do what I want I'll need to do something different...