Forum Discussion
Document Column Metadata Not Saving
Hello,
I've got a library of documents in a SharePoint Communications site. I added a column called "Project Type" and saved a number of project type options for that column (multi-select). However, when I select the relevant project types for a file and hit save, it shows "Saving..." then "Saved" but does not save the project type information. Instead, it just clears that field after saying it saved. I tried it multiple times and each time it shows like it is about to save those options for project type, then they go away.
I attached a video of what it looks like below.
Any advice on this?
Rohan
18 Replies
- kmktnnIron ContributorCheck if this helps:
In the application (Excel, Word, PowerPoint) > File > Options > Save:
• Click on 'Delete cached files'
• Check ‘Delete files from the office document cache when they are closed’
https://techcommunity.microsoft.com/t5/sharepoint/required-choice-column-reverts-to-previous-choice-in-library/m-p/3986404 - Bill-GunningCopper ContributorClose any Browser tab that may have the file open. Then check One Drive to see if the file has a green check and is not syncing. When you get the green check you should be able to updated the file properties.
- AndreaWRichardsonCopper Contributor
RoBhatt93 This is happening to me too. I first noticed it on a powerpoint, and now I am seeing it on an excel file. I removed the custom xml data from the powerpoint but this did not fix the issue. I haven't been able to test the excel doc as it is password protected at the moment. This is really frustrating and as noted by others is intermittent on native MS app items [PDFs never have issue]. Has anyone reached out to MS or found a true solution?
- ananto123Copper Contributor
AndreaWRichardson - I had this back in March with a document and cleared the Custom XML data in File Info and that did the trick then. It has turned up again and this time clearing Custom XML data didn't so I tried clearing Document Properties and Personal Information, which has worked.
- MiemieVCopper ContributorI am also experiencing this issue. Any easy way to fix this yet? A bit frustrating to not be able to use the metadata feature on documents.
- spstiboCopper ContributorI still have this issue any fix on it? except making a new column?
- Debbie_LeithCopper Contributor
I was having the same issue. I added a column called invoice number, I tired to add the invoice number for a particular excel file into the Invoice number column but I could not get it to save. I realized I had the excel file open. Once I closed the excel file the column comment saved.
- racrigBrass ContributorI have seen this issue fixed this issue by deleting the column and re-creating it. Not ideal of course if you have 1000s of documents. Export to Excel first to preserve all the values you'll have to copy back in.
- SpecialKSaundCopper ContributorHi all,
I'm having this same issue and wondering if there is another solution other than that proposed by Jack Wert. I have a lot of documents in this library and if I were to have to re-do the column, it would mean re-assigning that column's metadata to ALL of the files wouldn't it?
Thanks,
Karen- RobFischCopper ContributorI have run into this problem while working with Word documents. I seemed to have stumbled on a fix. I noticed in my source Word document there was some custom XML data in the metadata. After removing the custom XML, the issue is gone. I was not the author of the document so I have no idea where the custom XML came from, nor at this point, do I care. Problem fixed!
Here's the remedy I used...
Open the document in Word, click on File/Info/Check for Issues (Inspect Document)/Inspect Document/Inspect (button)/Remove All (Custom XML Data).- Maggi_CassellCopper ContributorThis worked for me, too. Thank you for sharing!
- Jack WertCopper Contributor
Hi All, Quick update on this issue.
I just tried recreating my choice columns and everything seems to work now. Literally copied and pasted the choices from the broken column into a new multi-select choice column in the original library. Same settings, documents, and only the default 'Document' content type. I guess this was just a transient issue on the back end associating the new Properties with specific Document IDs? Anyway, give it another try! Hope it works for you.