CHunky Universe of Vigourous Astonishing SHarepoint :)
Do you prefer REST over CSOM as I do? I’ll skip the whys. Andrew Connell put it already in wrtiting so nicely. Well, if you do prefer REST, then you must have discovered some shortcomings of REST, or its incompleteness compared to CSOM. I think of:
In such situations I was forced to use CSOM. Until yesterday. Yesterday I learned that we can actually use CAML queries in REST requests.
This enables using REST in all situations. The REST API is still developed and many features are added. Maybe a particular operation that needs a CAML query today, can be supported in the core REST API and can be easily refactored then.
But until then, we can use CAML queries in REST requests. Here are the important things about it:
HTTP headers you have to provide in REST requests with CAML queries
You can use jQuery or SP.RequestExecutor to make an ajax call. The REST endpoint is:
_api/web/Lists/GetByTitle('<your list title>')/GetItems
The request body (if you use json, and I bet, you do) is in this format:
{ "query" :
{"__metadata":
{ "type": "SP.CamlQuery" }
, "ViewXml": "<YOUR CAML QUERY>"
}
}
Here is the boilerplate for a REST request with a CAML Query:
function getDataWithCaml(listName, caml) {
var endpoint = "/_api/web/lists/GetByTitle('"
+ listName + "')/GetItems";
var requestData = { "query" :
{"__metadata":
{ "type": "SP.CamlQuery" }
, "ViewXml": caml
}
};
return jQuery.ajax({
url: endpoint,
method: "POST",
data: requestData,
headers: {
"X-RequestDigest": $("#__REQUESTDIGEST").val(),
"Accept": "application/json; odata=verbose",
"Content-Type": "application/json; odata=verbose"
}
});
}
This function is just an example. It has no error handling, and it takes for granted that your list is in the root site for on your (sub-)domain (“/”). So take it as an example only.
Here is how the function can be invoked
var caml = "<View><Query><Where><Or><Eq><FieldRef Name='AssignedTo' /><Value Type='Integer'><UserID/></Value></Eq><Membership Type='CurrentUserGroups'><FieldRef Name='AssignedTo' /> </Membership></Or></Where></Query></View>";
getDataWithCaml("Tasks", caml);
 | Anatoly Mironov on It is time to standardize the… |
 | Holger Küsgens on JSGrid Basics |
 | roshanjv on JSGrid Basics |
 | Filippo Bertuzzi on Export any web part from a Sha… |
| Filippo Bertuzzi on Export any web part from a Sha… |
 | Ben on Export any web part from a Sha… |
 | Fred on Export Any Web Part using a… |
| Fred on Export any web part from a Sha… |
 | Jasveer Singh on Publishing Visio diagrams as h… |
 | Syed Shoaib Adil on Make javascript code work with… |
VulaCV - Чăвашла вулаттаракан сайт
And going crazy doing it
Office 365, SharePoint and Azure
Nikander & Margriet on SharePoint
PFE @ Microsoft
Office 365, SharePoint, Azure, OnePlace Solutions & Life's Other Little Wonders
Me and My doings!
By Mohit Vashishtha
Erfarenheter, synpunkter och raljerande om Scrum från Jimmy Janlén
DevOps, Cloud and Blockchain Consultant
SharePoint for everyone
Ryan Dennis is a SharePoint Solution Architect with a passion for SharePoint and PowerShell
The Vision for a Future of Clarity
Treacle tarts for great justice
JavaScript, Web Apps and SharePoint
Mostly what I know about SharePoint - CommunicoCuspis
SharePoint på ren svenska
Nicely written! I too just learned that CAML was an option in REST as well!
Thank for your feedback. Appreciate it. It is so much in SharePoint. I am learning new things all the time. SharePointStack is a good place to gather knowledge.
Thanks for the great information, Anatoly. This is exactly what I needed. I stumbled into the limitation of REST and your post has helped me to find an easy solution.
спасибо за отзыв Михаил! Я видел что вы собираетесь поехать на SharePoint Saturday в Стокгольме http://sharepoint-community.net/events/sharepoint-saturday-stockholm/showAttendees?status=attending Тогда там встретимся.
Анатолий, к сожалению, в Стокгольм пока никак не получается, но возможно получится пересечься где-нибудь еще. Последние два года бывал на SharePoint Connect Amsterdam http://www.nccomms.com/sharepoint_connect/Home.aspx.
Анатолий, по теме поста столкнулся еще с одним вопросом, возможно Вы знаете ответ. Можно ли как-то организовать пэйджинг данным способом (в смысле CAML+Rest)? Т.е. как-то получить и впихнуть ListItemCollectionPosition в запрос? Пробовал, игрался всяко-разно, но пока никак. Есть какие-нибудь идеи?
I’m using this way to call “Pages” library. I found I have to make another call to server to get “FileRef” field value, directly calling CAML + REST API doesn’t return “FileRef” field value…it even doesn’t return file name…Do you have any luck?
Thanks for explaining this concept Anatoly, it’s very clear and well explained. I needed to make a REST call and use $filter on an “External Data” column; however, I would get an error that the field type of “BusinessData” could not be used in the query filter expression. So, instead, the method of using a CAML query helped me.
However, one thing that I was having trouble with using the CAML query w/ REST was this error:
{“error”:{“code”:”-1, Microsoft.SharePoint.Client.…-US”,”value”:”Not well formatted JSON stream.”}
I battled with this for a few hours, until my search brought me to a Stack Overflow answer that mentioned to used “JSON.stringify()” to format JavaScript strings/params to proper JSON format; so by wrapping the “requestData” in that function, I was able to successfully send the request to the server:
jQuery.ajax({
url:svcUrl,
method:”POST”,
data:JSON.stringify(requestData),
headers: {
“X-RequestDigest”:jQuery(“#__REQUESTDIGEST”).val(),
“Accept”:”application/json;odata=verbose”,
“Content-Type”:”application/json;odata=verbose”
},
success: function (data) {
console.log(data);
},
error: function (data) {
console.log(data);
}
});
Cool! I am glad that it worked out. Thanks a lot for sharing!
Thanks for posting this, very useful!
Thanks for sharing was helpful !!