Text Block migration

You can use the tool TBMigrate to load text fragments from third-party applications into KCM Repository as Text Blocks or Rich Text Blocks. Text Blocks must be present in the XML format used by KCM Repository and be stored in files with the .xml extension. Rich Text Blocks must be Microsoft Word documents (either .doc or .docx). Note, that the .doc format has been deprecated in KCM 5.7.0.

Loading Microsoft Word documents as Rich Text Blocks has the following limitations:

• Fields are not supported. The content of the documents is not checked for the presence of Fields and Field Sets, and no Fields or Field Sets are created in KCM Repository as a result of loading a Rich Text Block.
• No preview version of the Rich Text Block is created. Where a preview of the imported Rich Text Block is requested, the text "Preview not available" is shown. To generate a proper preview, edit the imported Rich Text Block and save it.

Also, Rich Text Blocks have the optional extra functionality that enables you to add a file with the same name as the Rich Text Block file and the extension .nfo, which contains additional information about the Text Block. You can add characteristics to a Rich Text Block by including characteristic:name or characteristic:group.name. There should be no additional whitespace. The characteristic and group are created if they did not previously exist.

Migrate Fields and Field Sets

Fields and Field Sets are not imported explicitly but created when Fields are being referenced in the Text Blocks. This behavior can be used if you need to create large amounts of Field Sets and Fields, for example, in a migration project. For this, create a dummy Text Block XML file, containing no text but only references to the Fields and Field Sets that should be created. After importing the file with the tool TBMigrate, you can delete the dummy Text Block from KCM Repository.