Quantcast
Channel: SharePoint 2013 - General Discussions and Questions forum
Viewing all articles
Browse latest Browse all 26374

Content types auto generating default content using required columns - Error - The file is locked for editing by another user. Notify When Available.

$
0
0

Our setup is the following:

SharePoint 2013

Clients Windows 7 & 8 X64 using Office 2013 X64

Using Document set on Document Libraries.

Default Content Word and Excel templates.

We create a new document set for each new project.  The document set is configured using a shared column to select the project number and added to the welcome page requiring the user to select the project number.  This works fine and the project number is synchronized to all documents that are auto-created from the Default Content.

 

Within the Content type settings we have configured several office templates to be used in the “Default Content section” which allows us to auto-generate these templates upon document set creation.  The office documents configured under default content are also configure to use a required column. 

When you edit the office documents created within the document set In SharePoint the required column works fine requiring you to enter an item and allowing you to save.  If however you first edit the document in Office the required column does not allow you to save.  The following error occurs Error - The file is locked for editing by another user.  Notify When Available. 

Since the file was just auto created by the document set clearly no one has the file open.  It is impossible to save this document with the category so essentially you have to close not saving.  Now if you go back and edit the properties VIA SharePoint

We can consistently reproduce this situation on different document libraries, content types, and columns.  It does not seem to be related to using the term store, normal columns, content type hub, etc.  The situation seems to be related specifically using the default content type to auto generate documents within the document set along with a required column.  Is this not supported?  Why are we able to edit the properties from the SharePoint Edit properties and save successfully however not with Word or Excel?

Any help or guidance on this would be greatly appreciated.



Viewing all articles
Browse latest Browse all 26374

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>