Open abdollahkahne opened 2 weeks ago
After some test and trials I get the following result: The SOAP API works always in case of Updating item/document but REST API apparently do not work for updating although it is okay with creation of item in case of single Taxonomy fields. In case of multi taxonomy both SOAP and REST approaches works. Both single column response same to APIs already with no difference. Possibly it was my mistake that I have though they were different
REST API also works for updating document metadata in case of uploading documents
Target SharePoint environment
SharePoint Server 2016 (on-premise)
What SharePoint development model, framework, SDK or API is this about?
SharePoint REST API
Developer environment
Windows
What browser(s) / client(s) have you tested
Additional environment details
No response
Describe the bug / error
I am using client side features of SharePoint to update an item which have three managed meta data column. One of them is multiple and should be update using hidden field associated with that column and I can update it with usual REST API. The other is a single term column and it can be updated similar to multi one. But the third column can not be update in same way. Actually it updates the item but It returns TaxCatchAll field only with just one term which is implicate an error in the item. I have to manually open the item in edit form and then save it without any change an everything get okay for TaxCatchAll endpoint. I believe that there is some step which is not done in this column by normal REST API. I try to update that column with other client side feature and I get same error in case of JSOM too. But fortunately I can solve the error with old SOAP APIs. I attached my code here and I appreciate every similar experience and the workaround for this problem. The following is my three version of code (REST API, JSOM and SOAP APIs):
Steps to reproduce
It is happened in this case and I am not sure how we can reproduce that bug in other environment. May be I can share that list as template!
Expected behavior
All Column behave similarly and as expected with REST APIs