RE: Managed Metadata Fields
Hi, In the past I used these two blog posts: http://blogs.msdn.com/b/sharepointdev/archive/2012/04/16/programmatically-create-a-managed-metadata-list-column-mohammed-faizan.aspx http://www.wictorwilen.se/Post/How-to-provision-SharePoint-2010-Managed-Metadata-columns.aspx They both use a feature receiver to link everything up. Wes From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Nigel Witherdin Sent: Wednesday, September 11, 2013 9:39 PM To: OzMoss Subject: RE: Managed Metadata Fields oops that went a bit early. Finished off below: From: nigel_wither...@hotmail.commailto:nigel_wither...@hotmail.com To: ozmoss@ozmoss.commailto:ozmoss@ozmoss.com Subject: Managed Metadata Fields Date: Thu, 12 Sep 2013 01:31:56 + Hey guys, Not a question this time - just a tip (NB I am working with SP2010, VS 2010). When I am creating solutions, I generally put together a proof of concept which includes the content types, lists, etc, which I then save as a WSP, and then import into Visual Studio to add the rest of the customizations. I generally only import the artifacts I need, not everything for the site, as I like my solutions to be as lean as possible. I have found however that with Managed Metadata fields pulled in this way, the field definition contains the environment specific properties: Property NameSspId/Name Value xmlns:q1=http://www.w3.org/2001/XMLSchema; p4:type=q1:string xmlns:p4=http://www.w3.org/2001/XMLSchema-instance;7437670e-a4f0-4f53-99ed-a9561766f7c5/Value /Property and Property NameTermSetId/Name Value xmlns:q2=http://www.w3.org/2001/XMLSchema; p4:type=q2:string xmlns:p4=http://www.w3.org/2001/XMLSchema-instance;9a2f696a-af3c-49cf-b186-1031f3f67113/Value /Property This means when you deploy this field onto another site collection using different termset Id's the field no longer works. A better way is to edit the field definitions (and schema.xml files if using list instances) and remove every property of a manged metadata field except for TextField. Alternatively, you can import your field definitions using the CKS toolkit, and it only brings across the TextId property. One last thing, edit your field definitions and remove all occurrences of the Version property (e.g. Version=1) - having a version defined on a field often means that if you try and update it through the UI after deployment, you will get an error message back saying field has been modified by another user. I would be interested to hear if others develop and package up field defs, content types etc through any other means?? Hope this helps someone out there ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
RE: Managed Metadata Fields
Thanks for the update, I’ll have to check that. Wes From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Nigel Witherdin Sent: Thursday, September 12, 2013 4:54 PM To: ozMOSS Subject: Re: Managed Metadata Fields Yeah I do the same thing and hook the mm field up to the termset through code, however if your field declaration includes the WebId or SiteId attributes, or the properties shown in my first post, then the field will appear to correctly hook up to the termset, but won't behave correctly. Instead what will happen is the correct value will be written to he hidden note field in the expected format of guid | label, but the associated mm or multi mm field won't be set correctly (it won't have a wssid value etc). So i suggest either generate your field declaration by hand and leave this stuff out, or edit the generated declaration and remove these attributes and properties Sent from my iPad On 13/09/2013, at 1:46 AM, Wes MacDonald wmacdon...@like10.commailto:wmacdon...@like10.com wrote: Hi, In the past I used these two blog posts: http://blogs.msdn.com/b/sharepointdev/archive/2012/04/16/programmatically-create-a-managed-metadata-list-column-mohammed-faizan.aspx http://www.wictorwilen.se/Post/How-to-provision-SharePoint-2010-Managed-Metadata-columns.aspx They both use a feature receiver to link everything up. Wes From: ozmoss-boun...@ozmoss.commailto:ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Nigel Witherdin Sent: Wednesday, September 11, 2013 9:39 PM To: OzMoss Subject: RE: Managed Metadata Fields oops that went a bit early. Finished off below: From: nigel_wither...@hotmail.commailto:nigel_wither...@hotmail.com To: ozmoss@ozmoss.commailto:ozmoss@ozmoss.com Subject: Managed Metadata Fields Date: Thu, 12 Sep 2013 01:31:56 + Hey guys, Not a question this time - just a tip (NB I am working with SP2010, VS 2010). When I am creating solutions, I generally put together a proof of concept which includes the content types, lists, etc, which I then save as a WSP, and then import into Visual Studio to add the rest of the customizations. I generally only import the artifacts I need, not everything for the site, as I like my solutions to be as lean as possible. I have found however that with Managed Metadata fields pulled in this way, the field definition contains the environment specific properties: Property NameSspId/Name Value xmlns:q1=http://www.w3.org/2001/XMLSchema; p4:type=q1:string xmlns:p4=http://www.w3.org/2001/XMLSchema-instance;7437670e-a4f0-4f53-99ed-a9561766f7c5/Value /Property and Property NameTermSetId/Name Value xmlns:q2=http://www.w3.org/2001/XMLSchema; p4:type=q2:string xmlns:p4=http://www.w3.org/2001/XMLSchema-instance;9a2f696a-af3c-49cf-b186-1031f3f67113/Value /Property This means when you deploy this field onto another site collection using different termset Id's the field no longer works. A better way is to edit the field definitions (and schema.xml files if using list instances) and remove every property of a manged metadata field except for TextField. Alternatively, you can import your field definitions using the CKS toolkit, and it only brings across the TextId property. One last thing, edit your field definitions and remove all occurrences of the Version property (e.g. Version=1) - having a version defined on a field often means that if you try and update it through the UI after deployment, you will get an error message back saying field has been modified by another user. I would be interested to hear if others develop and package up field defs, content types etc through any other means?? Hope this helps someone out there ___ ozmoss mailing list ozmoss@ozmoss.commailto:ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
Re: Managed Metadata Fields
Yeah I do the same thing and hook the mm field up to the termset through code, however if your field declaration includes the WebId or SiteId attributes, or the properties shown in my first post, then the field will appear to correctly hook up to the termset, but won't behave correctly. Instead what will happen is the correct value will be written to he hidden note field in the expected format of guid | label, but the associated mm or multi mm field won't be set correctly (it won't have a wssid value etc). So i suggest either generate your field declaration by hand and leave this stuff out, or edit the generated declaration and remove these attributes and properties Sent from my iPad On 13/09/2013, at 1:46 AM, Wes MacDonald wmacdon...@like10.com wrote: Hi, In the past I used these two blog posts: http://blogs.msdn.com/b/sharepointdev/archive/2012/04/16/programmatically-create-a-managed-metadata-list-column-mohammed-faizan.aspx http://www.wictorwilen.se/Post/How-to-provision-SharePoint-2010-Managed-Metadata-columns.aspx They both use a feature receiver to link everything up. Wes From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Nigel Witherdin Sent: Wednesday, September 11, 2013 9:39 PM To: OzMoss Subject: RE: Managed Metadata Fields oops that went a bit early. Finished off below: From: nigel_wither...@hotmail.com To: ozmoss@ozmoss.com Subject: Managed Metadata Fields Date: Thu, 12 Sep 2013 01:31:56 + Hey guys, Not a question this time - just a tip (NB I am working with SP2010, VS 2010). When I am creating solutions, I generally put together a proof of concept which includes the content types, lists, etc, which I then save as a WSP, and then import into Visual Studio to add the rest of the customizations. I generally only import the artifacts I need, not everything for the site, as I like my solutions to be as lean as possible. I have found however that with Managed Metadata fields pulled in this way, the field definition contains the environment specific properties: Property NameSspId/Name Value xmlns:q1=http://www.w3.org/2001/XMLSchema; p4:type=q1:string xmlns:p4=http://www.w3.org/2001/XMLSchema-instance;7437670e-a4f0-4f53-99ed-a9561766f7c5/Value /Property and Property NameTermSetId/Name Value xmlns:q2=http://www.w3.org/2001/XMLSchema; p4:type=q2:string xmlns:p4=http://www.w3.org/2001/XMLSchema-instance;9a2f696a-af3c-49cf-b186-1031f3f67113/Value /Property This means when you deploy this field onto another site collection using different termset Id's the field no longer works. A better way is to edit the field definitions (and schema.xml files if using list instances) and remove every property of a manged metadata field except for TextField. Alternatively, you can import your field definitions using the CKS toolkit, and it only brings across the TextId property. One last thing, edit your field definitions and remove all occurrences of the Version property (e.g. Version=1) - having a version defined on a field often means that if you try and update it through the UI after deployment, you will get an error message back saying field has been modified by another user. I would be interested to hear if others develop and package up field defs, content types etc through any other means?? Hope this helps someone out there ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
RE: Managed Metadata Fields
oops that went a bit early. Finished off below: From: nigel_wither...@hotmail.com To: ozmoss@ozmoss.com Subject: Managed Metadata Fields Date: Thu, 12 Sep 2013 01:31:56 + Hey guys, Not a question this time - just a tip (NB I am working with SP2010, VS 2010). When I am creating solutions, I generally put together a proof of concept which includes the content types, lists, etc, which I then save as a WSP, and then import into Visual Studio to add the rest of the customizations. I generally only import the artifacts I need, not everything for the site, as I like my solutions to be as lean as possible. I have found however that with Managed Metadata fields pulled in this way, the field definition contains the environment specific properties: PropertyNameSspId/Name Value xmlns:q1=http://www.w3.org/2001/XMLSchema; p4:type=q1:string xmlns:p4=http://www.w3.org/2001/XMLSchema-instance;7437670e-a4f0-4f53-99ed-a9561766f7c5/Value /Property and Property NameTermSetId/NameValue xmlns:q2=http://www.w3.org/2001/XMLSchema; p4:type=q2:string xmlns:p4=http://www.w3.org/2001/XMLSchema-instance;9a2f696a-af3c-49cf-b186-1031f3f67113/Value /Property This means when you deploy this field onto another site collection using different termset Id's the field no longer works. A better way is to edit the field definitions (and schema.xml files if using list instances) and remove every property of a manged metadata field except for TextField. Alternatively, you can import your field definitions using the CKS toolkit, and it only brings across the TextId property. One last thing, edit your field definitions and remove all occurrences of the Version property (e.g. Version=1) - having a version defined on a field often means that if you try and update it through the UI after deployment, you will get an error message back saying field has been modified by another user. I would be interested to hear if others develop and package up field defs, content types etc through any other means?? Hope this helps someone out there ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
Re: Managed Metadata fields become invalid after content migration - SP2010
Hi Prashanth, I wouldn't mind getting a copy of that, have you got it posted up anywhere? Kind Regards, Chris Tomich On 1 February 2011 11:49, Prashanth Thiyagalingam prashanth...@hotmail.comwrote: Hi Chris, I wrote a PS script based on yours with some tweaks on permissions, checkouts and approvals for publishing sites. It worked well for me. Thanks mate, appreciate it. Regards, Prashanth -- Date: Fri, 7 Jan 2011 15:00:11 +0800 Subject: Re: Managed Metadata fields become invalid after content migration - SP2010 From: chris.tom...@gmail.com To: ozmoss@ozmoss.com Hi Prashanth, I've encountered this problem before and wrote a powershell script to recurse through sites and lists to update the fields for you. Below is the link for the blog post that I have which has a brief explanation and the script. http://mymemorysucks.wordpress.com/2011/01/07/invalid-terms-in-managed-metadata-field/ Hope this helps. Kind Regards, Chris Tomich On 7 January 2011 13:57, Prashanth Thiyagalingam prashanth...@hotmail.com wrote: 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 http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
RE: Managed Metadata fields become invalid after content migration - SP2010
Hi Chris, I havent posted it yet, will do it soon and let you know. Regards, Prashanth Date: Fri, 4 Feb 2011 09:55:59 +0800 Subject: Re: Managed Metadata fields become invalid after content migration - SP2010 From: chris.tom...@gmail.com To: ozmoss@ozmoss.com Hi Prashanth, I wouldn't mind getting a copy of that, have you got it posted up anywhere? Kind Regards, Chris Tomich On 1 February 2011 11:49, Prashanth Thiyagalingam prashanth...@hotmail.com wrote: Hi Chris, I wrote a PS script based on yours with some tweaks on permissions, checkouts and approvals for publishing sites. It worked well for me. Thanks mate, appreciate it. Regards, Prashanth Date: Fri, 7 Jan 2011 15:00:11 +0800 Subject: Re: Managed Metadata fields become invalid after content migration - SP2010 From: chris.tom...@gmail.com To: ozmoss@ozmoss.com Hi Prashanth, I've encountered this problem before and wrote a powershell script to recurse through sites and lists to update the fields for you. Below is the link for the blog post that I have which has a brief explanation and the script. http://mymemorysucks.wordpress.com/2011/01/07/invalid-terms-in-managed-metadata-field/ Hope this helps. Kind Regards, Chris Tomich On 7 January 2011 13:57, Prashanth Thiyagalingam prashanth...@hotmail.com wrote: 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 http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
RE: Managed Metadata fields become invalid after content migration - SP2010
Hi Chris, I wrote a PS script based on yours with some tweaks on permissions, checkouts and approvals for publishing sites. It worked well for me. Thanks mate, appreciate it. Regards, Prashanth Date: Fri, 7 Jan 2011 15:00:11 +0800 Subject: Re: Managed Metadata fields become invalid after content migration - SP2010 From: chris.tom...@gmail.com To: ozmoss@ozmoss.com Hi Prashanth, I've encountered this problem before and wrote a powershell script to recurse through sites and lists to update the fields for you. Below is the link for the blog post that I have which has a brief explanation and the script. http://mymemorysucks.wordpress.com/2011/01/07/invalid-terms-in-managed-metadata-field/ Hope this helps. Kind Regards, Chris Tomich On 7 January 2011 13:57, Prashanth Thiyagalingam prashanth...@hotmail.com wrote: 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 http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
RE: Managed Metadata fields become invalid after content migration - SP2010
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 http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
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 + 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 http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
RE: Managed Metadata fields become invalid after content migration - SP2010
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 + 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.commailto:ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
RE: Managed Metadata fields become invalid after content migration - SP2010
Also see this http://technet.microsoft.com/en-us/library/ff851878.aspx From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Jeremy Thake Sent: Friday, 7 January 2011 2:42 PM To: ozMOSS Subject: RE: Managed Metadata fields become invalid after content migration - SP2010 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 + 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.commailto:ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
Re: Managed Metadata fields become invalid after content migration - SP2010
Hi Prashanth, I've encountered this problem before and wrote a powershell script to recurse through sites and lists to update the fields for you. Below is the link for the blog post that I have which has a brief explanation and the script. http://mymemorysucks.wordpress.com/2011/01/07/invalid-terms-in-managed-metadata-field/ Hope this helps. Kind Regards, Chris Tomich On 7 January 2011 13:57, Prashanth Thiyagalingam prashanth...@hotmail.comwrote: 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 http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
RE: Managed Metadata fields become invalid after content migration - SP2010
Hi Jeremy, Thanks for the info, I didnt move the Managed Metadata Service Application DB, will go through the link Thanks, Prashanth 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:44:38 + Also see this http://technet.microsoft.com/en-us/library/ff851878.aspx From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Jeremy Thake Sent: Friday, 7 January 2011 2:42 PM To: ozMOSS Subject: RE: Managed Metadata fields become invalid after content migration - SP2010 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 + 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 http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
RE: Managed Metadata fields become invalid after content migration - SP2010
Thanks Chris, will give it a shot. Regards, Prashanth Date: Fri, 7 Jan 2011 15:00:11 +0800 Subject: Re: Managed Metadata fields become invalid after content migration - SP2010 From: chris.tom...@gmail.com To: ozmoss@ozmoss.com Hi Prashanth, I've encountered this problem before and wrote a powershell script to recurse through sites and lists to update the fields for you. Below is the link for the blog post that I have which has a brief explanation and the script. http://mymemorysucks.wordpress.com/2011/01/07/invalid-terms-in-managed-metadata-field/ Hope this helps. Kind Regards, Chris Tomich On 7 January 2011 13:57, Prashanth Thiyagalingam prashanth...@hotmail.com wrote: 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 http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
