RESTful call to unlock file?

Greetings all!

When SP2013 has Versioning enabled, but force checkout is NOT enabled -- this is supposed to be for collaborative editing or some similar feature.  If you edit a file (say in MS Word), SP "locks" the file for a period of time.  I read that the default is 30min, but I am finding that it is 60min in my environment.  SP then automatically creates a new "version" of the file with the accumulated changes.  More frequent times results in more versions - but more granular edits, of course.

I am looking for a way to "force" SP to perform its unlock (and merge/check-in) before the timeout period.  I do not want to "break the lock" and discard changes.  I simply want to tell SP not to wait until the default time to run its background versioning/unlocking on the file.

Does anyone know of a way to issue a RESTful call to tell SP to do this?

EDIT: I _think_ what I'm trying to do is update the SPFile.SPCheckOutStatus ?  Basically change the CheckoutExpires to "now" or null, maybe?  I notice that there is a "short-term lock" and a "long-term lock" flavor.  Don't know if I would have to do something different for each, but unlocking the file "immediately" is the goal -- via a RESTful call?

Thanks in advance,

August 17th, 2015 10:22pm

There is no REST API to force Microsoft Word to unlock or expire a local copy of the SharePoint file.
Free Windows Admin Tool Kit Click here and download it now
August 18th, 2015 6:50pm

Right, looks like only the server side SPFile.ReleaseLock() is there.

Too bad the office apps don't release the lock when they're done editing the file.  We have to wait somewhere between 10 and 60min before we can edit them further (as a different user).

August 18th, 2015 9:27pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics