-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot update File's term (managed metadata) property if the file is a .docx, .xlsx, ect. #1503
Comments
The issue occurs using any of SystemUpdateAsync() and UpdateOverwriteVersionAsync(). |
Out of curiosity to make sure I'm not going insane.. I am changing the extension of the file via code to .tmp. The .tmp file allows the term to be set. |
I ran the following code after to see what the client sees..
editedFile.ListItemAllFields Values contains a null entry for the term fields, while file.ListItemAllFields Values related to the terms remain populated. |
@IllumiC : is this currently still an issue? Feels much like a temporary system glitch... |
Category
Describe the bug
I use the following code to obtain the file properties and load the relevant data to edit its properties.
I use the following code to edit the TermFieldName property.
I have tested this on the file extensions pdf, jpg, txt, odt, rtf, doc, docx and xlsx.
All extensions other than docx and xlsx have their files update both the TermFieldName and Subject. Docx and xlsx updates the Subject but not the TermFieldName.
Steps to reproduce
Use ListItemAllFields to update a term (managed metadata) alongside any other fields. When attempting on a docx or xlsx file, the term field will not be populated, but other fields are in the same UpdateOverwriteVersionAsync() call. file.ListItemAllFields.Values shows the term field guid.
Expected behavior
The TermFieldName will be populated.
Environment details (development & target environment)
Additional context
No error is displayed. All other fields are updated, however the term fields are ignored.
Both fields are required. There are other optional fields and required fields which are not always populated.
The file is newly created using PnP Core SDK prior to attempting to edit it.
The text was updated successfully, but these errors were encountered: