Forum Discussion
Issue with renaming large files before upload is complete
ChrisWebbTech , they are working in Teams and, according to the person reporting the issue, typically "drag the files into Teams" (no idea if they're using the web client or desktop app). The (potential) problem with the sync option is that the files in question are video recordings of clinical therapy sessions and some of the clinicians are working on personal (not University-provided/managed) devices without proper encryption or other security measures, so storing them locally on the machine violates one or more privacy regulations. The videos are recorded locally using Zoom. The clinicians have been instructed - immediately after the conclusion of a session - to upload them, ensure the upload was successful (ie: play the video), then delete the file from their device. While they insist that everyone is following that protocol, I suspect they are skipping the "ensure the upload was successful" part.
- Can always utilize files on demand and instead of delete once “moved” and synced can turn it to Online only which will remove the local copy, but that might be too much overhead.
They have updated Teams file tab in the past few months so that could be the culprit of the issue. There was a way you can load up and link to an online only (WebDAV) link to SharePoint libraries. This might be an option as welll.ChrisWebbTech Yeah, if these folks can't wait for a file to finish uploading to rename it, then expecting them to wait and check that it's finished syncing, then right-click and "free up space" is just asking way too much. Thanks for the info and suggestions, though. To be clear, I saw the same behavior whether I was uploading directly to a SP Doc Lib or the Files tab in Teams (browser or desktop app). The only discrepancy is that in SP, the file appears in the library as soon as the upload starts, while in Teams (either front end), the file name doesn't show up until the upload finishes OR you do a manual refresh of the Files tab.
In any case, SharePoint should (IMO), either lock the file from changes until the upload is complete or (better) queue changes so that they aren't actually applied until the file is all there.
Chad_V_Kealey it usually does I thought. Maybe only on file edits. Anyway, the "Open with Explorer" option could work, but the negative is it requires Internet Explorer to work. That works like a direct network drive to the Library location.