List properties web part showing unselected fields after item is edited

Brass Contributor

I've noticed (what I think is) a bug with the 'List properties' web part in SharePoint Online. Here's what I'm doing:

  • I add a 'Document library' web part to a SharePoint modern site page and choose a document library.
  • I add a 'List properties' web part to the same page.
  • I connect the 'List properties' web part to the 'Document library' web part.
  • I set 'Allow users to edit list items' to 'On'.
  • In the 'Select fields to display' section of the 'List properties' web part, I select four of the ten fields (my Document library has ten fields).

What do I expect?

  • When I select an item in the 'Document library' web part, I expect the four fields that I selected to display in the 'List properties' web part to appear for the selected document.
  • I expect to be able to edit any of those four fields.
  • When I finish making my edits to any or all of the four fields, I still only see the four fields I selected to display.

What happens?

  • The four fields that I selected to display in the 'List properties' web part to appear for the selected document. GOOD! :smile:
  • I can edit any of the four fields. GOOD! :lol:
  • When I finish my edits to any or all of the four fields, ALL of the ten fields are then displayed and are editable. NOT SO GOOD! :sad:

 

Is this a bug? I really think it is and if so, can someone at Microsoft take a look into this and hopefully fix it?

 

Thanks.

4 Replies
10 months since I posted this and no reply. The issue is still present. How do I escalate this to someone at Microsoft?
Hi Joe

I am experiencing exact same today, came here to see if anyone else in similar situation and what response is, disappointing that nobody has even acknowledged the issue!!

I'm not sure where to raise bugs but would like to know too, I'll do another post to ask

It's super frustating that I went into quite a lot of details to explain the problem and got no reply. Glad someone else is experiencing the problem as I thought I was alone (obviously I'm not glad that it is causing you problems personally!). Hopefully someone from Microsoft can comment and escalate this as an issue, and fix it!

I have the same issue. I'm adding my comment here as well in hopes that Microsoft addresses this.