Project Description
SPServices is a jQuery library which abstracts SharePoint's Web Services and makes them easier to use. It also includes functions which use the various Web Service operations to provide more useful (and cool) capabilities. It works entirely client side and
requires no server install.
Be sure to read IMPORTANT NOTES below.
| Like SPServices? Support my work. | Follow @jQSPWS and/or @sympmarc on Twitter. | Follow SPServices (jQSPWS) on Facebook |
 |  |
RECENT NEWS and BLOG POSTS:
- 2013-02-28 - The march to v2013.01 has begun!
- SPServices Stories - An ongoing blog series about how SPServices is used in the wild. Have a story? Let me know!
- 2013-02-22 -SPServices Futures: Moving to jQuery’s Deferred Objects and More
- 2013-02-05 - SPServices Compatibility Issues with jQuery 1.9.1
- 2013-01-29 - SPServices Compatibility Issues with the Minified Version of jQuery 1.9.0
- 2012-11-13 -Where Should SPServices Go Next? Common Question at SPC12
- 2012-09-24 - jQuery Library for SharePoint Web Services (SPServices) v0.7.2 Released
- 2012-09-12 - Generic Error Handling in SPServices
- If you'd like to use SPServices from a CDN, you can!SPServices is on cdnjs. There are links to the individual versions on eachDownload page. Available versions: 0.7.2, 0.7.1a, 0.7.0, 0.6.2, 0.6.1, 0.6.0, 0.5.8. Thanks to Ryan Kirkman (@ryan_kirkman) at cdnjs for getting things set up initially and Josh McCarty (@joshmcrty) for adding new versions for me.
IMPORTANT NOTES
- 2013-02-05 - SPServices will *not* work with jQuery 1.9.1 due to a bug in that release. See my blog post above.
- 2013-01-29 - SPServices works just fine with jQuery 1.9.0, but NOT with the minified version. If you need to use jQuery 1.9.0, please stick with the non-minified version or minify your own version. See my blog post above. This is a known issue with jQuery 1.9.0, which the team has already fixed for the next version. Here's the bug in the jQuery bug tracker:http://bugs.jquery.com/ticket/13274.
- If you want to use SPServices with jQuery 1.8.x, you MUST upgrade to SPServices v0.7.2 or greater.
- If you want to use SPServices with jQuery 1.7.x, you MUST upgrade to SPServices v0.7.0 or greater. The jQuery team made a change in 1.7 which prevents the .find("[nodeName='z:row']") syntax from working. See my blog post for more details. If you are using this notation, DO NOT upgrade to jQuery 1.7 without adjusting your code to use the newSPFilterNode function. This will impact not just SPServices, but any of your own code which uses the .find("[nodeName='z:row']") syntax.
- SPServices v0.5.8 and earlier do not work with jQuery 1.5+. With SPServices v0.5.8 and earlier, you'll need to stick with jQuery 1.4.x. See my blog post for details.
START HERE: Here are some ways in which you can get started with this library:
- If this is your first visit, you might want to check the FAQs. If your initial questions aren't covered there, then leave a post in theDiscussions and I'll get back to you ASAP.
- Read the documentation. It constantly amazes me how many people seem to skip this step. I've spent a lot of time writing it, and many of your questions are already answered there.
- Search the Discussions. Literally thousands of others have used this library and many have asked questions in the Discussions. What you need to know may already have been asked and answered there.
- Read the articles about this library at NothingButSharePoint.com's EndUserSharePoint channel or my blog.
- Read what others are saying about SPServices on the Articles and Press page
Sympraxis Consulting LLC (aka Marc D Anderson) is developing the jQuery Library for SharePoint Web Services. For a demo of some of this library's capabilities (some a bit dated), please check out the demo site. Tell me what you're using the library for -- I'd love to post some stories about how you are solving real problems. Contact me directly. Or review the library at SharePointReviews.com by clicking on the badge below. Also see the Credits page for the ever-evolving list of people who have helped somewhere along the way. I want this library to be very useful and the development to be community-driven so that it can become a de facto standard. (Lofty goal, but there you go.) If there's something that you'd like to see me implement, add a Discussion item. If you see a bug, tell me in the Issue Tracker. I also welcome code submissions and any interest to help.
Since you're here, you might want to check out my other Codeplex project: