SharePoint Document Library Templates Save Location

%3CLINGO-SUB%20id%3D%22lingo-sub-2220601%22%20slang%3D%22en-US%22%3ESharePoint%20Document%20Library%20Templates%20Save%20Location%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2220601%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20the%20following%20scenario%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3EI%20have%20a%20document%20library%20configured%20to%20always%20open%20in%20desktop%20app.%3C%2FLI%3E%3CLI%3EI%20have%20predefined%20document%20types%20with%20template%20word%20docs%20linked%20to%20them%3C%2FLI%3E%3C%2FUL%3E%3CP%3EWhen%20I%20user%20selects%20%22New%22%20from%20the%20document%20library%20drop%20down%20and%20selects%20a%20document%20template%2C%20the%20document%20opens%20in%20Word%20but%20the%20default%20save%20location%20isn't%20picked.%20The%20user%20then%20has%20to%20go%20back%20and%20find%20the%20location%20again%20to%20save%20the%20document.%20My%20work%20around%20right%20now%20is%20to%20turn%20off%20the%20Always%20Open%20in%20Desktop%20App.%26nbsp%3B%20Have%20the%20template%20document%20get%20created%20in%20the%20library.%20Then%20the%20user%20pick%20Edit%20in%20Desktop%20app.%20This%20isn't%20ideal%20because%20people%20get%20confused%20that%20they%20are%20not%20in%20the%20desktop%20app%20at%20times%20and%20some%20document%20feature%20do%20not%20work%20in%20the%20web%20app.%20For%20instance%20Linked%20Meta%20data%20fields%20do%20not%20populate.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20work%20around%20or%20trick%20to%20make%20this%20work%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2220601%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDocument%20Library%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2220855%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Templates%20Save%20Location%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2220855%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F408711%22%20target%3D%22_blank%22%3E%40NThoman%3C%2FA%3EI%20have%20the%20same%20exact%20issue%20as%20you%20and%20have%20not%20been%20able%20to%20make%20this%20work%20as%20expected%20which%20renders%20SharePoint%20useless%20for%20this%20very%20common%20requirement.%20In%20my%20case%20I%20have%20document%20properties%20in%20the%20document%20as%20fields%20which%20require%20the%20use%20of%20the%20Word%20application%20(not%20the%20browser).%20I%20would%20never%20attempt%20the%20workaround%20you%20are%20using%20as%20my%20users%20would%20never%20in%20a%20million%20years%20figure%20this%20out.%20The%20site%20has%20many%2C%20many%20libraries%20so%20it%20is%20not%20reasonable%20to%20expect%20them%20to%20figure%20out%20where%20to%20put%20this%20(and%20the%20document%20properties%20wouldn't%20work%20anywhere%20else%20anyway).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20appears%20to%20be%20a%20complete%20miss%20by%20Microsoft...%20just%20straight%20up%20doesn't%20work%20the%20way%20we%20want%20it%20to%20(i.e.%20the%20way%20any%20normal%20user%20would%20expect%20it%20to).%20Hoping%20someone%20can%20prove%20that%20I'm%20wrong%20about%20this...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2222939%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Templates%20Save%20Location%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2222939%22%20slang%3D%22en-US%22%3EI%20was%20really%20hoping%20someone%20was%20going%20to%20respond%20with%20I%20was%20doing%20something%20stupid.....%3CBR%20%2F%3E%3CBR%20%2F%3EDidn't%20this%20work%20with%20On-Prem%20in%202016%20and%202013%3F%20I%20thought%20it%20did.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20noticed%20a%20new%20issue%20with%20my%20work%20around.%20The%20option%20to%20%22Open%20in%20Desktop%20App%22%20seems%20to%20be%20missing%20for%20some%20people%20recently.%20Not%20sure%20if%20this%20is%20caused%20by%20permissions%20(I%20do%20have%20the%20list%20locked%20down%20since%20it%20is%20related%20to%20HR%20Employee%20Information)%20or%20an%20update%20to%20how%20the%20Web%20App%20now%20loads.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2223344%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Templates%20Save%20Location%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2223344%22%20slang%3D%22en-US%22%3EFigured%20out%20my%20issue%20with%20the%20%22Open%20in%20Desktop%20App%22%20issue.%20I%20had%20a%20custom%20roll%20for%20managers%20to%20approve%20documents%20but%20they%20also%20needed%20the%20permission%20%22Use%20Client%20Integration%20Features%22.%3C%2FLINGO-BODY%3E
Occasional Contributor

I have the following scenario:

 

  • I have a document library configured to always open in desktop app.
  • I have predefined document types with template word docs linked to them

When I user selects "New" from the document library drop down and selects a document template, the document opens in Word but the default save location isn't picked. The user then has to go back and find the location again to save the document. My work around right now is to turn off the Always Open in Desktop App.  Have the template document get created in the library. Then the user pick Edit in Desktop app. This isn't ideal because people get confused that they are not in the desktop app at times and some document feature do not work in the web app. For instance Linked Meta data fields do not populate.

 

Is there a work around or trick to make this work?

6 Replies

@NThomanI have the same exact issue as you and have not been able to make this work as expected which renders SharePoint useless for this very common requirement. In my case I have document properties in the document as fields which require the use of the Word application (not the browser). I would never attempt the workaround you are using as my users would never in a million years figure this out. The site has many, many libraries so it is not reasonable to expect them to figure out where to put this (and the document properties wouldn't work anywhere else anyway).

 

This appears to be a complete miss by Microsoft... just straight up doesn't work the way we want it to (i.e. the way any normal user would expect it to). Hoping someone can prove that I'm wrong about this...

I was really hoping someone was going to respond with I was doing something stupid.....

Didn't this work with On-Prem in 2016 and 2013? I thought it did.

I noticed a new issue with my work around. The option to "Open in Desktop App" seems to be missing for some people recently. Not sure if this is caused by permissions (I do have the list locked down since it is related to HR Employee Information) or an update to how the Web App now loads.
Figured out my issue with the "Open in Desktop App" issue. I had a custom roll for managers to approve documents but they also needed the permission "Use Client Integration Features".
Also there is no way to use a Adobe PDF fillable form as a SharePoint document library template. This also will not work. It's hard to believe that this monstrosity called Office 365 cannot decently accommodate this dead simple Clerical task... This is hard to report to the people who pay for this stuff. I would use this hundreds of times if it actually worked. Meanwhile they roll out mixed reality in PowerApps and whatever the latest Teams feature is that nobody cares about. I would just be happy if the absolute basics, things that Google docs has done for years, would work.
By the way, even if the save location worked as expected, all of the word documents created using the library's docx template (I know about the dotx thing) that has controls in it are corrupt and cannot be opened so I guess it doesn't really matter because it wouldn't work anyway :worried_face:

Simple requirement would be for user to click the new button, open a template with controls in it in the Word application, click save and close and have the document save in the library, with the values from the Word controls mapped to the columns as document properties without a bunch of convoluted workarounds that the average user would never figure out. individual pieces of this work but to put the whole thing together cannot be surfaced to a group of users without a bunch of crazy workarounds therefore it is all useless.
Same annoying issue on multiple tenants here, there is not much info on this I was glad to find this thread.