Move To/Copy To is restricted to same library in SharePoint 2019

%3CLINGO-SUB%20id%3D%22lingo-sub-1133907%22%20slang%3D%22en-US%22%3EMove%20To%2FCopy%20To%20is%20restricted%20to%20same%20library%20in%20SharePoint%202019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1133907%22%20slang%3D%22en-US%22%3E%3CP%3EHopefully%20this%20is%20the%20right%20place%20to%20ask%20this.%20I%20have%20a%20SharePoint%202019%20server%20on%20prem%20and%20just%20noticed%20that%20the%20Move%20To%20and%20Copy%20To%20functions%20are%20only%20able%20to%20move%2Fcopy%20within%20the%20same%20library.%20The%20selection%20for%20a%20different%20location%20is%20not%20available%20to%20change.%20I've%20read%20articles%20saying%20if%20you%20wan%20to%20have%20different%20sites%20listed%20as%20targets%20you%20need%20to%20enable%20scripting.%20I've%20not%20set%20that%20up%20as%20I'm%20not%20trying%20to%20move%20between%20sites%2C%20just%20move%20to%20a%20separate%20library%20on%20the%20same%20site.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20was%20on%20a%20call%20with%20MS%20SharePoint%20support%20today%20for%20a%20different%20issue%20and%20asked%20about%20this.%20They%20confirmed%20it's%20the%20same%20behavior%20in%20every%20SharePoint%202019%20build%20they%20have%20access%20to%2C%20and%20in%20all%20their%20configurations.%20So%20their%20assessment%20was%20that%20it's%20either%20a%20true%20bug%20or%20it's%20by%20design.%20I%20thought%20I'd%20come%20here%20and%20look%20for%20some%20feedback%20since%20that%20felt%20a%20little%20hasty%20of%20an%20assessment.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20anyone%20confirm%20if%20this%20is%20working%20for%20them%20and%20what%20it%20took%20to%20get%20it%20there%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1133907%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1135116%22%20slang%3D%22en-US%22%3ERe%3A%20Move%20To%2FCopy%20To%20is%20restricted%20to%20same%20library%20in%20SharePoint%202019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1135116%22%20slang%3D%22en-US%22%3EI%20think%20this%20is%20by%20design%20and%20the%20full%20feature%20we%20have%20in%20SPO%20was%20not%20ported%20at%20the%20time%20they%20made%20the%20branch%20for%20the%20SP%202019%20build%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1135809%22%20slang%3D%22en-US%22%3ERe%3A%20Move%20To%2FCopy%20To%20is%20restricted%20to%20same%20library%20in%20SharePoint%202019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1135809%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F60%22%20target%3D%22_blank%22%3E%40Juan%20Carlos%20Gonz%C3%A1lez%20Mart%C3%ADn%3C%2FA%3E%26nbsp%3BThanks%20for%20the%20quick%20reply%2C%20even%20though%20it's%20disheartening.%20How%20are%20you%20seeing%20people%20move%20larger%20datasets%3F%20My%20OneDrive%20sync%20is%20currently%20broken%2C%20open%20MS%20case%20on%20that%2C%20Explorer%20view%20has%20been%20deprecated%20in%20favor%20of%20OneDrive%20and%20now%20I'm%20finding%20out%20that%20Move%20To%2FCopy%20To%20doesn't%20function%20properly.%20How%20is%20the%20average%20company%20replacing%20that%20functionality%3F%20I%20know%20the%20proper%20answer%20is%20they%20use%20SPO%2C%20and%20believe%20me%2C%20I'm%20on%20board%20with%20that%2C%20but%20for%20this%20client%20it%20wasn't%20an%20option.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hopefully this is the right place to ask this. I have a SharePoint 2019 server on prem and just noticed that the Move To and Copy To functions are only able to move/copy within the same library. The selection for a different location is not available to change. I've read articles saying if you wan to have different sites listed as targets you need to enable scripting. I've not set that up as I'm not trying to move between sites, just move to a separate library on the same site.

 

I was on a call with MS SharePoint support today for a different issue and asked about this. They confirmed it's the same behavior in every SharePoint 2019 build they have access to, and in all their configurations. So their assessment was that it's either a true bug or it's by design. I thought I'd come here and look for some feedback since that felt a little hasty of an assessment.

 

Can anyone confirm if this is working for them and what it took to get it there?

2 Replies
Highlighted
I think this is by design and the full feature we have in SPO was not ported at the time they made the branch for the SP 2019 build
Highlighted

@Juan Carlos González Martín Thanks for the quick reply, even though it's disheartening. How are you seeing people move larger datasets? My OneDrive sync is currently broken, open MS case on that, Explorer view has been deprecated in favor of OneDrive and now I'm finding out that Move To/Copy To doesn't function properly. How is the average company replacing that functionality? I know the proper answer is they use SPO, and believe me, I'm on board with that, but for this client it wasn't an option.