File Lock Override
Site/folder/file owners should be able to unlock locked files (waiting an hour for SharePoint to realise I closed that document it opened for me in Word Online is a real pain).
Chris P commented
Over two years and nothing has been done on this. More people need to vote.
Spencer Chen commented
Owners should be given the option to wield the POWER.
very much needed
Dennis (Castra) commented
So, when is this going to be implemented in SharePoint 2016?
Why there is a long delay in fixing this BUG.. :( This is a daily issue at my office and my users are really really not happy to see their files are locked by themselves!!
Locked by me and I cannot move the file...crazy.
Jeff Hilyard commented
I encountered "locked for shared use by me" as the only user of a Word Doc in Teams (moving from Teams client to Word client and unable to save) while demonstrating to my IT colleagues the benefits of collaborating with Teams Files. The idea that end-users would encounter that experience killed any interest.
Extremely frustrating user experience. I am the only one using the file, yet I cannot edit it because it has been locked by... myself. I closed all browsers and it's still locked.
This should not be a suggestion! Get it together MS, stop being abusive on your customers!
I found another workaround:
Simply use another browser! You should now be able to checkout the file you have problems with and check it back in.
After that use your original browser.
Greetings from Germany
Ole Kristian Mørch-Storstein commented
can anyone consistently facing this issue have a look at this blog post and see if changing the flag allow-sync-xhr-in-page-dismissal to "enabled" does anything? (full disclaimer, im the author of this blog-post)
JL Sandin commented
Wow!!! More than a year and issue still worlking on, waiting for a solution from Microsoft. After googling, I could only find out to requesto for this "feature" as a fix for this problem. I've voted, but I do not think this will work out the problem...
Jon Paarlberg commented
This issue just took the excitement out of our O365 SharePoint initial launch. We worked for months to get away from file locking issues in SharePoint 2010, 2013 and were so happy to finally be able to collaborate.
Imagine everyone's impression when they were unable to collaborate because of a file locking issue.
Why are we voting for this like it is a fun, custom feature instead of a seriously broken and badly needed fix?
Why do we have so many useless features when the core functionality is so flawed that very few can stand to use it?
Such frustration for my end users.
This is a serious issue for us as well. Really wish there was a way out remove orphan locks
Annie Davis commented
Saying "We don't know how to resolve this" does not instill confidence in the abilities of an IT department. Getting real tired of asking users to try again in 10-30 minutes.
This is a serious problem, happened multiple times in our organization. It cost me too much time on just working this simple issue out.
Anne H. commented
This is one of the #1 issues we have across our 400-user environment. People were slow to adopt SharePoint and this issue is a real hindrance for us.
Ignacio Ortiz commented
I'm on your same boat Saroj, when these small things make everyone's life difficult it's extremely counterproductive to adoption.
Saroj Gilbert commented
I try to be open to Microsoft, but it is issues like this that make it really difficult. Sorry, MS, but you have a serious usability problem here. Just fix the damned thing. Forget about how many votes you get. Just fix it. and if you can't get to the ultimate "fix", provide a viable work-around by allowing the "owner" of the folder to unlock any file that ends up in a locked status. In case it isn't obvious, you need to allow the ownership of a folder to be changed since employees don't stay in their position forever. I would suggest you defer to the owner of the folder above to have that privilege. In our case sometimes our users (nearly all volunteers with other commitments) simply forget to check the file back in... regardless of the reason, your SharePoint customers need a way to unlock a file.