Are you getting an error like “The SPListItem being updated was not retrieved with all taxonomy fields” when you try adding or modifying values in a TaxonomyField of a list item in SharePoint? Then read ahead, I’ve got a quick and dirty solution!
Reason
After quick googling and some frustration, I figured the probable reason for the issue. SharePoint went and broke the link between the internal Note-field and the actual TaxonomyField you’re supposed to be using. And this causes SharePoint to return slightly confusing errors.
Term Store Management Tool for managing (for example) the termsets associated with your Taxonomy Fields
In my case, my app actually just got a simple JSON response {“The SPListItem being updated was not retrieved with all taxonomy fields.”} I’d see this error any time I was trying to modify or create any values of a field of type TaxonomyField. I used OfficeDev.PnP’s TaxonomyExtensions to achieve this, but also tried the “normal” CSOM libraries – and the result was always the same. No amount of ctx.Load(item) -calls would help 😉
Like so many times with SharePoint, the solution’s simple, yet frustrating. Continue reading
Related Posts:
Tweaking the SharePoint list view search box to filter on managed metadata fields
Fixing the error: “Column XX in table dbo.YY is of a type that is invalid for use as a key column in an…
RefinableString -managed property in SharePoint Online not populating for all items
Alternative Languages in SharePoint forcing the (cumbersome) use of localized Managed Properties
