Last year, we released enhancements that allow you to copy files in Office 365. Today, we're adding the ability to move files in Office 365 with full fidelity protections for metadata and version ma...
I'm curious if any of the backslapping comments here have actually tested this functionality?
I welcome the feature being put back (Content and Structure has been with us for over a decade lads, let's not pretend this is a new feature please).
My query relates to a fairly common application of a move function, and that's from one library in an SPWeb to another library in the same Web, which doesn't seem to be supported. Is this an omission or simple user error?
I have two content types, both derived from the same parent content type, itself derived from 'Document', one for Documents, one for Photos, with a single additional field for the Photos CT.
Each Web has exactly two libraries, one each for Docs and Photos, with 1 content type apiece.
When a file is misfiled, zips of photos in this test case, they need to be moved to the correct library. This doesn't appear to be a supported scenario.