Skip to content
Branch: master
Find file History
andrewconnell Merge remote-tracking branch 'origin/master'
Conflicts:
	SpRestBatchSample/README.md
Latest commit d47459c Feb 18, 2015
Permalink
Type Name Latest commit message Commit time
..
Failed to load latest commit information.
Contacts Added batch REST sample Oct 8, 2014
Content Added batch REST sample Oct 8, 2014
Features/Feature1 Added batch REST sample Oct 8, 2014
Images Added batch REST sample Oct 8, 2014
Package
Pages fixed initial import of this project (previously committed a 'stage' … Oct 8, 2014
Scripts added update capability and removed unnecessary header values Dec 7, 2014
AppManifest.xml fixed initial import of this project (previously committed a 'stage' … Oct 8, 2014
README.md Merge remote-tracking branch 'origin/master' Feb 18, 2015
SpRestBatchSample.csproj fixed initial import of this project (previously committed a 'stage' … Oct 8, 2014
SpRestBatchSample.sln Added batch REST sample Oct 8, 2014
packages.config Added batch REST sample Oct 8, 2014

README.md

Sample SharePoint Hosted App that demonstrates how to do simple REST operations with the SharePoint 2013 REST API.

For an explanation on how batching works, see these two blog posts:

This demonstrates how to do simple CRUD operations but also demonstrates how to create batches of individual requests. Checking the batch button on the page will force the app to use the OData $batch operator when adding, deleting & updating the drivers. This will issue a single HTTP request instead of a series of HTTP requests... a significant performance improvement!

Watch the browser console or use a HTTP debugging proxy like Fiddler to watch the traffic sent across.

Note: for the update & delete operations to work, you must first insert drivers for all three teams first. No error checking has been added to ensure you only add one team's drivers once in the list.

Applies To:

  • SharePoint 2013 On-premises (versions: TBD)
  • Office 365 SharePont Online (versions: TBD)

Known Issues:

  • The batch response coming back from SharePoint's REST API is not including changeset references as per the OData v3.0 & v4.0 spec indicate that it should. However the order of the responses coming back from the batch request match the order of the requests in the initial batch request.

Analytics

You can’t perform that action at this time.