2012年4月17日 上午 03:30
I have read that Microsoft does not support translation when managed metadata is being imported using CSV. I am wondering is there any easier and best way to do it ? I have three different environments, I would not want to create hundreds of translated terms in all three environments manually.
I can maybe create it in one environment and then export/import it to the others, but was not able to find a way to do it.
Is this can only be done via custom code using taxonomy API ?
2012年4月17日 上午 05:29
It can be done via custom code, or you could use a tool created by somebody else, such as this one: http://metadataexportsps.codeplex.com/ For term sets, you can use http://sharepointdragons.com/2012/04/12/moving-your-taxonomy-to-a-production-environment/
- 已編輯 Margriet Bruggeman 2012年4月17日 上午 05:30
2012年4月17日 下午 01:30
I think the both tool uses CSV Import in the back end and I am afraid these tool will not support translated terms. I have no problem exporting and importing term sets but I have two languages to select from and I have a default label set for each language and I am not sure how I can import both the english and its translated default label using CSV.
2012年6月22日 下午 06:22
Well, I ended up writing the custom code to get this done. Simple code to loop through the groups->terms sets-> and terms and then copy it to XML along with translated term and then in my import routine, I generated the same hierarchy keeping the same guids.
- 已標示為解答 OttawaTechGuy 2012年6月22日 下午 06:23