Forum Discussion
Office 365 - Recreating the SharePoint issues.
Thanks Eric, for all the ideas and pointers.
The user must be on CTR (Click-to-run) as she recently did the 'Online Repair', which effectively removes the already installed office and installs the latest one.
The assertion basically is that user worked on the file for about 2 hours and made lot of changes, and after checking-in the file there was no new version saved, instead the version shown was the version that the user started from. There was no trace of the user ever checked out the document and made any changes. So the user did not see the version created for her on check-in.
We will have our central admin check with MSFT representative.
Thanks again.
>after checking-in the file there was no new version saved
Did the user save the doc and/or upload the changes, prior to checking in? If not, simply checking in the file does NOT force the upload of changes. This is sort of a common misconception for many users, especially those who've used systems that present an upload step in the Check-In process/screens.
1. Check out file
2. Download (or, Open in Client app from SharePoint)
3. Edit, then Save (and upload if manually downloaded)
4. Check-in
Thanks Kevin, The user did save the file multiple times and in fact SharePoint library did show user's name and new timestamp against the document while it was checked out to the user. The user edited in client application instead of downloading the file.
I would look in the audit logs with the Security Centre, and see what the user really did. There really isn't a likelihood that the user saw a fully successful check-in and then the file just dissapeared without a trace.
Thanks Steven. We didn't have the auditing turned on to save on SPO resources (CPU and Storage). We should turn it on, I will check with our central admin. Thanks for the pointer.
