Forum Discussion
versioning fails when copying
Hi mtarler,
I thought a custom permission level would work but it did not. I could not find a site, document library or versioning setting that would help either.
This is not ideal, but you can create a trigger to notify you when a file is deleted using Power Automate. This will provide an opportunity to intervene and restore the file (and version history) from the site recycle bin.
I hope this helps.
Norm
We have the exact same setup in my organisation (a separate Working Library), and this issue still seems to be occurring in SharePoint document libraries space. Does anyone know if the links to documents also break when using the 'move to' and 'copy to' functions? As this is essentially creating a 'new item' rather than actually replacing a file - does this mean a new link is created too? It is really not ideal and creating a bit of an administration nightmare having to relink everything.
When you use Move To or Copy To in SharePoint Online:
- If the file name is the same in the destination library: SharePoint will not create a duplicate. Instead, it will treat the incoming file as an update to the existing one. The destination file will get a new version added on top of the existing version history.
- If the file name is different in the destination library: SharePoint will create a new file entirely, with its own item ID and version history starting fresh.
Hi Virendrak,
Thanks for the reply, although this doesn't ring true in my experience. When using the 'Move To' function to move a document out of the working library into the controlled library - where previous versions already exist - even with the file name being exactly the same, all previous versions seem to be overwritten and lost.