Text Block migration

The tool TBMigrate has been created in order to load text fragments from third-party applications into the ITP/MDK Repository as Text Blocks or Rich Text Blocks. TBMigrate only manages (Rich) Text Blocks, not Forms or Views. Text Blocks must be present in the XML format used by the ITP/MDK Repository, and be stored in files with the .xml extension. Rich Text Blocks must be Microsoft Word documents (either *.doc or *.docx).

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 the ITP/MDK 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, e.g. in the Content Wizard Editor or in an ITP/OnLine Server model run, the text "Preview not available" is shown. To generate a proper preview, edit the imported Rich Text Block and save it.

Migrate Fields and Field Sets

Fields and Field Sets are not imported explicitly, but created on the fly when Fields are referenced in the Text Blocks. This behavior can be used if it is needed 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 TBMigrate the dummy Text Block can be deleted from the ITP/MDK Repository.