"Required Properties" error opening SharePoint online DOCX with more than 50 term set items

%3CLINGO-SUB%20id%3D%22lingo-sub-904575%22%20slang%3D%22en-US%22%3E%22Required%20Properties%22%20error%20opening%20SharePoint%20online%20DOCX%20with%20more%20than%2050%20term%20set%20items%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-904575%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3ESummary%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EFor%20a%20month%20or%20two%20my%20document%20editors%20have%20been%20opening%20word%20documents%20from%20a%20SharePoint%20library%20and%20getting%20%22required%20properties%22%20error%20preventing%20them%20from%20saving%20the%20file.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAfter%20much%20testing%20we've%20found%20the%20cause%20is%20setting%20a%20managed%20meta%20data%20column%20to%20have%20more%20than%2050%20term%20set%20items%20as%20the%20default%20column%20values.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20found%20this%20very%20hard%20to%20find%20any%20information%20about%20so%20I%20wanted%20to%20post%20here%20so%20that%20there%20is%20something%20for%20others%20to%20find%2C%20and%20to%20gauge%20how%20much%20of%20an%20issue%20this%20is.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EIdeally%20I'd%20love%20it%20if%20the%20Word%2FSharePoint%2FOneDrive%20teams%20updated%20the%20message%20displayed%20in%20word%20to%20let%20people%20know%20that%20the%20issue%20isn't%20missing%20required%20metadata%20but%20the%20number%20of%20metadata%20items%20in%20one%20property.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EIf%20you%20want%20my%20test%20methodology%20and%20results%20let%20me%20know%20and%20I'll%20post%20it%20below.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EEnvironment%3A%20%3C%2FSPAN%3E%3C%2FP%3E%3CUL%3E%3CLI%3E%3CSPAN%3ESharePoint%20online%20document%20library%2C%20custom%20content%20type%2C%20with%20a%20location%20column%2C%20with%2062%20possible%20managed%20meta%20data%20term%20set%20items%20available.%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EThe%20default%20content%20type%20for%20the%20library%20is%20the%20custom%20content%20type.%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EThe%20SharePoint%20online%20document%20library%20Location%20column%20has%20default%20values%20set%2C%20which%20equal%20all%20the%20items%20in%20the%20termset.%20So%20each%20document%20put%20into%20the%20library%20gets%20all%2062%20terms%20added%20to%20it%E2%80%99s%20location%20property.%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EWindows%202010%20laptop%2C%20running%20Word%202016%20desktop%20app.%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EUser%20editing%20the%20word%20document%20is%20a%20%E2%80%9Cmember%E2%80%9D%20of%20the%20site%20so%20has%20edit%20rights%20to%20the%20sharepoint%20online%20document%20library.%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%3CSPAN%3EThe%20use%20case%3C%2FSPAN%3E%3C%2FP%3E%3CUL%3E%3CLI%3E%3CSPAN%3EA%20user%20uploads%20a%20document%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EIt%20receives%20the%20default%20custom%20content%20type%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EBecause%20of%20the%20custom%20content%20type%20it%20gets%20the%20Location%20property%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EBecause%20the%20default%20values%20for%20the%20location%20property%20are%20set%20to%20all%2062%20location%20items%20the%20document%E2%80%99s%20location%20property%20gets%2062%20term%20set%20items%20added%20to%20it.%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EWhen%20the%20user%20opens%20the%20document%20in%20word%20online%20they%20can%20edit%20the%20content%20of%20the%20document%20and%20it%20saves%20with%20no%20problems%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EWhen%20the%20user%20opens%20the%20document%20in%20the%20Word%20Desktop%20App%20(Word%202016%20in%20this%20case)%2C%20they%20get%20the%20%E2%80%9CRequired%20properties.%20To%20save%20to%20the%20server%20correct%20the%20invalid%20or%20missing%20required%20properties%E2%80%9D%20message.%3C%2FSPAN%3E%3CUL%3E%3CLI%3E%3CSPAN%3EAfter%20much%20testing%20I%20have%20proved%20(to%20myself%20at%20least)%20that%20this%20message%20is%20NOT%20correct.%20Word%2C%20OneDrive%20and%20SharePoint%20teams%20take%20note.%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EThis%20message%20also%20occurs%20when%20a%20Managed%20Meta%20data%20property%20contains%20more%20than%2050%20items%20%2C%20when%20the%20user%20opens%20the%20file.%20Note%20I%20say%20when%20the%20user%20opens%20the%20file.%20If%20the%20property%20contains%2040%20items%20and%20the%20user%20opens%20the%20document%20in%20Word%202016%20they%20can%20add%2020%20more%20items%20and%20save.%20But%20when%20they%20open%20it%20again%20they%20get%20the%20error.%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FUL%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%3CSPAN%3EThe%20solution%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E-%20For%20me%20this%20is%20going%20to%20be%20tricky%2C%20but%20I%20have%20to%20find%20a%20way%20of%20allowing%20for%20all%20usecases%20around%20location%20specific%20documentation%20while%20not%20giving%20every%20document%20all%2062%20of%20our%20location%20terms.%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E-%20Your%20suggestions%20welcome%20%3A)%3C%2Fimg%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-904575%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOneDrive%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESites%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-907670%22%20slang%3D%22en-US%22%3ERe%3A%20%22Required%20Properties%22%20error%20opening%20SharePoint%20online%20DOCX%20with%20more%20than%2050%20term%20set%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-907670%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F228833%22%20target%3D%22_blank%22%3E%40Dorje%20McKinnon%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20original%20post%20that%20go%20me%20thinking%20that%20this%20might%20be%20the%20issue%20was%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fen-US%2F666ed281-e91d-4aea-85ec-1eaf5848e8f8%2Frequired-properties-missing-just-started-happening%3Fforum%3DOffice2016ITPro%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fen-US%2F666ed281-e91d-4aea-85ec-1eaf5848e8f8%2Frequired-properties-missing-just-started-happening%3Fforum%3DOffice2016ITPro%3C%2FA%3E%3C%2FP%3E%3CP%3EThanks%20David%20L%20Jenkins%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fsocial.technet.microsoft.com%2Fprofile%2Fdavid%2520l.%2520jenkins%2F%3Fws%3Dusercard-mini%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsocial.technet.microsoft.com%2Fprofile%2Fdavid%2520l.%2520jenkins%2F%3Fws%3Dusercard-mini%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1035620%22%20slang%3D%22en-US%22%3ERe%3A%20%22Required%20Properties%22%20error%20opening%20SharePoint%20online%20DOCX%20with%20more%20than%2050%20term%20set%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1035620%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20issue%20also%20occurred%20in%20our%20environment.%20We%20are%20unable%20to%20save%20document%2C%20in%20Word%20app%2C%20which%20has%20more%20than%2050%20terms%2C%20error%20message%20%22required%20properties%22%20is%20appeared.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20someone%20solved%20the%20issue%2C%20or%20know%20the%20root%20cause%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20also%20raised%20MS%20premium%20support%20ticket.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1036856%22%20slang%3D%22en-US%22%3ERe%3A%20%22Required%20Properties%22%20error%20opening%20SharePoint%20online%20DOCX%20with%20more%20than%2050%20term%20set%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1036856%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F470402%22%20target%3D%22_blank%22%3E%40cebud%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20didn't%20find%20any%20solution%20for%20this%20from%20MS%2C%20or%20in%20our%20extensive%20searching%20and%20discussions%20with%20other%20experts%20in%20the%20field.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20we%20changed%20the%20way%20we%20did%20our%20meta%20data%2C%20rather%20than%20adding%20all%20site%20locations%20individually%20to%20each%20document%2C%20we%20created%20an%20%22All%20sites%22%20metadata%20item%20and%20use%20that%2C%20only%20changing%20it%20where%20required.%3C%2FP%3E%3CP%3EIn%20our%20case%20if%20a%20document%20didn't%20relate%20to%20all%20sites%20it%20only%20related%20to%201%2C%202%20or%20up%20to%205%20so%20the%2050%20limit%20wasn't%20an%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Frequent Contributor

Summary

For a month or two my document editors have been opening word documents from a SharePoint library and getting "required properties" error preventing them from saving the file.

 

After much testing we've found the cause is setting a managed meta data column to have more than 50 term set items as the default column values.

 

I found this very hard to find any information about so I wanted to post here so that there is something for others to find, and to gauge how much of an issue this is.

Ideally I'd love it if the Word/SharePoint/OneDrive teams updated the message displayed in word to let people know that the issue isn't missing required metadata but the number of metadata items in one property.

If you want my test methodology and results let me know and I'll post it below.

 

Environment:

  • SharePoint online document library, custom content type, with a location column, with 62 possible managed meta data term set items available.
  • The default content type for the library is the custom content type.
  • The SharePoint online document library Location column has default values set, which equal all the items in the termset. So each document put into the library gets all 62 terms added to it’s location property.
  • Windows 2010 laptop, running Word 2016 desktop app.
  • User editing the word document is a “member” of the site so has edit rights to the sharepoint online document library.

The use case

  • A user uploads a document
  • It receives the default custom content type
  • Because of the custom content type it gets the Location property
  • Because the default values for the location property are set to all 62 location items the document’s location property gets 62 term set items added to it.
  • When the user opens the document in word online they can edit the content of the document and it saves with no problems
  • When the user opens the document in the Word Desktop App (Word 2016 in this case), they get the “Required properties. To save to the server correct the invalid or missing required properties” message.
    • After much testing I have proved (to myself at least) that this message is NOT correct. Word, OneDrive and SharePoint teams take note.
    • This message also occurs when a Managed Meta data property contains more than 50 items , when the user opens the file. Note I say when the user opens the file. If the property contains 40 items and the user opens the document in Word 2016 they can add 20 more items and save. But when they open it again they get the error.

The solution

- For me this is going to be tricky, but I have to find a way of allowing for all usecases around location specific documentation while not giving every document all 62 of our location terms.

- Your suggestions welcome :)

3 Replies

This issue also occurred in our environment. We are unable to save document, in Word app, which has more than 50 terms, error message "required properties" is appeared.

 

Has someone solved the issue, or know the root cause?

 

We have also raised MS premium support ticket.

Hi @cebud 

We didn't find any solution for this from MS, or in our extensive searching and discussions with other experts in the field.

 

So we changed the way we did our meta data, rather than adding all site locations individually to each document, we created an "All sites" metadata item and use that, only changing it where required.

In our case if a document didn't relate to all sites it only related to 1, 2 or up to 5 so the 50 limit wasn't an issue.