I have a focus on System Engineering for O365/Azure Solutions. In doing this I very often encounter customer wishes that can't be met without coding and scripting. That's what I'm gonna write about!
We saw that this particular issue was only caused by users first editing documents in Office Online, never by anyone using the client applications directly without first opening in Office Online. When testing against SharePoint onprem we also saw in the ULS logs that (shared) file locks were initialized when opening in office online, but the locks were apparently never released. This also had some side effects like the current user appearing multiple times in the "people editing this document" box. So pulling on this thread i tried to figure out how the actual lock is removed when using office online, but for the affected users no XHR traffic appeared when navigating away from Office Online.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
How did you figure out this issue arises because of this flag? I would never have guessed!
We saw that this particular issue was only caused by users first editing documents in Office Online, never by anyone using the client applications directly without first opening in Office Online. When testing against SharePoint onprem we also saw in the ULS logs that (shared) file locks were initialized when opening in office online, but the locks were apparently never released. This also had some side effects like the current user appearing multiple times in the "people editing this document" box. So pulling on this thread i tried to figure out how the actual lock is removed when using office online, but for the affected users no XHR traffic appeared when navigating away from Office Online.