Skip to main content
added 1 characters in body
Source Link
sptek
  • 216
  • 2
  • 12

After inspecting the library items with Sharepoint Manager, I discovered that the field values are different. The term and GUID are identical (in both the visible and the the *TaxHTfield0 hidden field) but the prefixed numbernumbers in the visible field are different.

Which probably makes sense, as they AFAIK are lookup values to the taxonomy hidden list, and the reused term and the original will have different entries there.

I was hoping there would be some timer job to clean up behind the scenes after this kind of reconfiguration, but I guess I need to do some scripted changes instead.

After inspecting the library items with Sharepoint Manager, I discovered that the field values are different. The term and GUID are identical (in both the visible and the the *TaxHTfield0 hidden field) but the prefixed number in the visible field are different.

Which probably makes sense, as they AFAIK are lookup values to the taxonomy hidden list, and the reused term and the original will have different entries there.

I was hoping there would be some timer job to clean up behind the scenes after this kind of reconfiguration, but I guess I need to do some scripted changes instead.

After inspecting the library items with Sharepoint Manager, I discovered that the field values are different. The term and GUID are identical (in both the visible and the the *TaxHTfield0 hidden field) but the prefixed numbers in the visible field are different.

Which probably makes sense, as they AFAIK are lookup values to the taxonomy hidden list, and the reused term and the original will have different entries there.

I was hoping there would be some timer job to clean up behind the scenes after this kind of reconfiguration, but I guess I need to do some scripted changes instead.

Source Link
sptek
  • 216
  • 2
  • 12

After inspecting the library items with Sharepoint Manager, I discovered that the field values are different. The term and GUID are identical (in both the visible and the the *TaxHTfield0 hidden field) but the prefixed number in the visible field are different.

Which probably makes sense, as they AFAIK are lookup values to the taxonomy hidden list, and the reused term and the original will have different entries there.

I was hoping there would be some timer job to clean up behind the scenes after this kind of reconfiguration, but I guess I need to do some scripted changes instead.