SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have tried 2 scenarios to update the term store data (on a wiki page content type) 1.) I update a term and hit up and the changes are not reflected on a content type (wiki page) where I am using that meta data item. After making the term item update (changing text) and navigating back to the wiki page I inspect the properties and the value is not showing the updated value.

2.) The other scenario...I have also tried to merge term store items. In view mode the page property shows the old label value. When I go into edit mode it shows the correct value which is good however this also would require me to navigate to every page go into edit mode and hit update/save on the page (in order to get the correct property value).

How can I get the label value of the meta data to update (when making changes to the term store).

I have found this article and ensured that the Taxonomy Update Scheduler is executing but the term values are not getting updated.

NOT sure where to look now. Any ideas would be appreciated.


share|improve this question
Did you ever get this resolved? I'm having the same problem on a site. Kind regards, Jurgen – user7931 Apr 19 '12 at 12:51
David DId you had a solution for this? – user11091 Oct 3 '12 at 17:47
We are having the same issue with SharePoint 2013 (March CU). I read somewhere about a hidden field that needs to be updated.… But I wasn't able to get this working in my environment. – user29643 Jun 13 '14 at 11:46
up vote 1 down vote accepted

I have the same problem and have been researching this evening. Going to follow this guy's advice for a workaround until a fix is released for this issue:

share|improve this answer
I am finding that after running this ps script, I still need to perform and edit/save operation on each item to be complete. Submitted to Microsoft and waiting for solution. – David Feb 8 '12 at 16:23
Thanks David. I'm about to do the same. Do post when you get a solution. – zazie Feb 8 '12 at 23:14
Apparently SharePoint 2010 sp1 resolves the issue. We currently have sp1 and our immediate problem is not resolved, however while working with Microsoft we found an exception being thrown by the taxonomy service. At this point, we do not know the source of the issue. However if you have updated to sp1 and still have a problem turn on logging and look for exception. I will try to remember to update this post when we get things resolved. – David Feb 23 '12 at 2:01

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.