Forum Discussion
Sharepoint Save Nightmare
Thanks for clarifying. If the issue also occurs when the file is not checked out and nobody else is editing it, then this may be related to changes not reaching SharePoint rather than a co-authoring conflict.
When this happens, check the Unsaved Changes pane in Excel. Microsoft documents that changes can remain waiting to be uploaded to the cloud. You can also check File > Info > Version History to see whether the change reached SharePoint.
If the change is visible in Excel but does not appear in Version History, that would help narrow down where the problem is occurring.
The issue still occurs when not using the check out feature. Users are reporting that simple data entry into their files is not saving. I can also attest that even when not checking out files, and nobody else is in the file, and autosave is enabled, data is sometimes lost.
Thank you, but this does not solve the issue
Thanks for clarifying. If the issue also occurs when the file is not checked out and nobody else is editing it, then this may be related to changes not reaching SharePoint rather than a co-authoring conflict.
When this happens, check the Unsaved Changes pane in Excel. Microsoft documents that changes can remain waiting to be uploaded to the cloud. You can also check File > Info > Version History to see whether the change reached SharePoint.
If the change is visible in Excel but does not appear in Version History, that would help narrow down where the problem is occurring.
Thank you. I've realized the save issues are due to two reasons - the files are large, ranging from 10-30 MB, and they are .xlsm file type, which to my understanding requires the entire file to be uploaded to OneDrive & Sharepoint, rather than individual changes made to cells. This is an issue because we often have multiple users in the same file at once, but due to the .xlsm file type the changes are pretty much never able to sync in real time - one of the users will have to completely re-download the workbook. This is an issue that really should be made more clear; it took many hours of research to realize this was the problem. I'm not saying it should be fixed, but Microsoft should show a warning for .xlsm file types that their compatibility with Co-Authoring is severely limited, or basically nonexistent.