-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use <Method> in SPServices #79
Comments
That doesn't look like valid CAML to the SOAP (asmx) services. |
It's a valid caml. |
As Mark indicated - it is not valid for the legacy SOAP API which SPServices still uses to interact with SharePoint. You are correct that it is ok for CSOM (or other more recent APIs) - the key here is that SPServices uses the SOAP API services which have not been updated in long time (sp2007?) and are considered legacy. I would suggest that you use the docs to refer to the old MS soap services documentation which should help get your CAML defined correctly.
My the way: it would help ALOT if you actually posted your JavaScript code that shows the call to SPServices so that we further understand what actual SOAP operation is being used. It also helps us to help you, by enable us to use that code to run quick tests to see if we can identify potential problems and suggest a solution.
Paul
…-- sent from mobile
|
Thanks Paul |
You need to build it as a SOAP request (XML) and I think the method that needs to be used is the GetListItems... Here are some links that might help you:
If you happen to respond back to this thread - Please include your JS code that shows your setup to the SPServices |
I can't find any solution to write query like this in SPServices:
<View> <Method Name="<The name of the Read List method which we edited to add the Filter>"> <Filter Name="<The name of the Filter>" Value='{0}'/> </Method> <Query> <Where> <Eq> <FieldRef Name='<Name of the Filter Field>' /> <Value Type='Number'>{0}</Value> </Eq> </Where> </Query> </View>
The text was updated successfully, but these errors were encountered: