Receiving the error "Some files are missing required metadata. Fix file issues now." but when clicked no files displayed

Question

Firstly... tried to include images for this problem and received errors - both for pasting and uploading.

Using SharePoint Online

Here's what I have done:

1. Create a Content Type in the Content Type Gallery in SharePoint Admin Center, that has managed metadata and people columns that re Required.
2. Within an existing Team Site,
   Add the Content Type - using the new approach, from a Document Library, Add Column -> Add a Content Type (repeat, library has 4 Content Types)
3. Make the Content Type the default and remove Document as a Content Type in this library

To reproduce the error:

1. Create a new document in Word and save to this library
2. Save the document, prompted to choose Content Type and then message appears re missing metadata, complete all metadata
3. Retry Save
4. Document is saved and appears in SharePoint.
5. Refresh page. Errors appears. "Some files are missing required metadata. Fix file issues now." and documents appear with the little red icon (tag with a ?)
6. Hover over a document with this error. Window appears with "Missing required info" and link to "Add information now"
7. All columns have values and no errors are shown.

(Note: also tried creating a new document from the New menu - no difference in outcome).

If I click the link "Fix file issues now" in the error message for the Document Library, it changes the view to "Files that need attention" and no files are shown.

I wondered if there were any hidden required fields. Used PnP Powershell to check on the Content Type. 8 fields have Required = True - and these are they ones I created. Nothing else is Required.

I have 4 Content Types. What I have noticed is that 2 Content Types work fine and 2 cause this issue. The 2 Content Types with the error have 4 people columns that are required.

Any ideas on how to resolve this so that there are no errors for missing metadata?

Answer 1

I had the exact same problem and - after quite a bit of analysis - I reached the following conclusion

The metadata message appears if :

1. The list contains a people column
2. That column is required
3. The column is not part of the selected view
4. The column is set to be displayed as Name (with presence)

If you don't want the column in the view you can change the display to 'Name' and the missing metadata warning disappears.

This clearly seems to be a bug to me ;-)

Answer 2

I agree this was really helpful, and I was able to silence the incorrect error message by modifying my views, but I have instances where a particular view has extra columns that weren't needed for the business... I agree definitely buggy

I had the exact same problem and - after quite a bit of analysis - I reached the following conclusion

The metadata message appears if :

1. The list contains a people column
2. That column is required
3. The column is not part of the selected view
4. The column is set to be displayed as Name (with presence)

If you don't want the column in the view you can change the display to 'Name' and the missing metadata warning disappears.

This clearly seems to be a bug to me ;-)

Answer 3

Thanks for that.

So I just did what you did - I added the required fields to the current view and the icon disappears. Remove the fields the icon comes back.

Curious. A bit annoying but I can live with that.

If I get time I'll take a look at the API results.

Answer 4

Dear Chris,

I did a test and I can't reproduce the issue in our environment.

I suggest you first use the API call to see if all values are populated into the required People type column and the required Managed Metadata type column.

For example, in your environment, the managed metadata column is SiteMetadata and the people column is SitePeople in the content type in the site library.

_api/web/lists/getbytitle('DocumentLibrary01')/Items(@{items('Apply_to_each')?['ID']})?$expand=SitePeople&$select=SitePeople/EMail,SiteMetadata&$select=SiteMetadata/Label,FileLeafRef

Use the call below in a flow to see the body result. If the values aren't populated successfully, You can also use the Get files action in the flow to see if all fields are populated with the values.

Welcome to share any updates when you have time if you need further help on this issue.

Thanks for your effort and time!

Sincerely,

Cliff | Microsoft Community Moderator

Answer 5

Dear Chris,

Thanks for your updates and kindness.

Welcome to share any updates at your convenience.

Thanks for your effort and time!

Sincerely,

Cliff | Microsoft Community Moderator