Tuesday
Jul312012
SP2013 Custom services deploys and runs on v15
Tuesday, July 31, 2012 at 12:56AM
I fired up my SP2013 VM to do some simple tests tonight, I wanted to know if the REST services that I've built and demo'ed for SharePoint 2010 would run in SP2013. Technically, they should.
So I deployed:
- stsadm -o addsolution -filename .\SPGSvcWp.wsp
- stsadm -o deploysolution -name SPGSvcWp.wsp -local -allowgacdeployment -allcontenturls
The files are copied to the services OK.
Deployed to ISAPI folder (_vti_bin)
DataService
REST service
SOAP service
Activate the features for the webpart:
Add the Web Part to the page:
The javascript needs a small modification - since the page in 2013 is loaded asynchronously. But once I've re-attached the click event, the REST service itself works fine and returns the properties of the selected item.
in
SharePoint
SharePoint 





Reader Comments (2)
Hello John. Great blog - 34 pages of really useful sharepoint/infopath insights. Are you up for suggestions. Still struggling to find a solution to recording a reference number for each item logged to a sharepoint list. Went through lots of sites saying why you shouldn't add a reference of your own, and have now found from lots of sites that the ID field cannot be displayed at all when creating a record, nor easily afterwards. What do you suggest as a way to automatically create a sequential number for each record created - or to display the ID of each record. Understand this won't be possible on record creation so would need an action to email to the record creator details of the record they have just created and include in that the ID reference. Ideally would want to be able to do the solution in sharepoint with or without SPD and Infopath as our IT folks lock out opportunities to use scripts, jquery etc. Thanks again for inspiring stuff!
Hi MikeMc, have you looked at SharePoint's Document ID service? It tags all documents created within a site collection with a unique ID, and then make that item reachable in combination with the Search Service. There are some limited control over how you'd prefix the IDs, or if you have code access, you can write your own plugin to generate unique ID for the documents.