So are you backing up the Managed Metadata Service Application DB from Test and restoring the DB over the one in Production? E.g. so all the Terms are in the Termstore with the same Guids?
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Prashanth Thiyagalingam Sent: Friday, 7 January 2011 2:16 PM To: ozmoss@ozmoss.com Subject: RE: Managed Metadata fields become invalid after content migration - SP2010 Yes I am doing this programatically via the feature receiver and its the Term Set is linked to the field correctly, but the existing terms are shown in red as invalid and I need to click the term and point it again to make it valid ________________________________ From: jth...@made4the.net To: ozmoss@ozmoss.com Subject: RE: Managed Metadata fields become invalid after content migration - SP2010 Date: Fri, 7 Jan 2011 06:08:38 +0000 So if you go in and create a new List Item and modify a Site Column that is mapped to the Term Set...does this allow you to pick terms or not? From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Prashanth Thiyagalingam Sent: Friday, 7 January 2011 1:58 PM To: ozmoss@ozmoss.com Subject: Managed Metadata fields become invalid after content migration - SP2010 Hi All, After migrating content (stsadm backup/restore) from UAT to PROD, the metadata fields in pages show the error 'The term is not a valid term'. I know the link between metadata field and the Term Store is broken during the content migration and I have re linked it using a feature but still the Terms are shown as invalid. Any help would be appreciated. Thanks, Prashanth _______________________________________________ ozmoss mailing list ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com> http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
_______________________________________________ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
