Forum Discussion
AngelaJ1s
Nov 24, 2021Copper Contributor
Disable SharePoint List Attachments - Form still showing 'Add attachments' field.
Hi,
I have a modern SharePoint Online list in which I have disabled attachments using the List Settings > Advanced Settings > Attachments = Disabled. When creating new list items, the form that appears still shows add attachments and it will still allow you to add and then give an error. When you edit and item, no field for adding an attachment to the list item shows.
When I go back into the advanced list settings, the attachments setting is still disabled but there is a tick in the box 'Add attachments column to default view'. I have tried unchecking this option, but when I save and go back to this page, the box is still checked.
Help, how can I hide the attachments option from even showing on the form?
- Thanks, I checked mine and once I unchecked the "Add attachments column to default view" in advanced settings, it removed it from my form!
 
19 Replies
- Ben LeachCopper ContributorHmm...I'm not sure why the modern UI would still show attachments if advanced settings have been configured to disable them...sounds like a setting that is a leftover from classic lists isn't being respected in modern lists for some reason.
If you want more control over what fields are being displayed, a simple approach would be to customise the form using PowerApps, then you can choose which fields are displayed and explicitly exclude the Attachments field from the form.
You would need to disable Edit in Grid View and Properties Pane from the list advanced settings to make sure that the user always followed the path of editing in the customised form. This approach also gives a lot more flexibility on how you visually present the fields, including being able to group them and create section headings etc.
So in summary, if I was presented with the challenge of disabling attachments, that is probably the approach I would look at first- GailTremblayCopper ContributorI am experiencing the same issue for several of my SharePoint lists. Is there a possibility that is a temporary bug on Microsoft end? Hopefully we can find a fix soon!