This post is on personal title and meant to help / share feedback how to use content importer for scenarios using batch import in older versions of Tridion Docs/Knowledge Center/LiveContent/Trisoft.

One important note is that content importer and batch import work differently in many perspectives. So there is not a like for like mapping for the main scenarios using batch import.

One important tip when testing content importer is to clean the import history every now and then:

1. Close content importer if it is running
2. Go to the folder %localappdata%\SDL\InfoShare Client\14.0\Imports
3. Make sure that windows explorer is enable to show hidden files
4. Remove all the files in this folder

After these steps content importer will startup with a clean desk.

In these posts I use the term 'item' that refers to (a resolution of) a language of a version of logical object It also refers to a file with a filename of the form '<Title>=<Logical ID>=<Version>=<Language>=<Resolution>.<Extension> where <Resolution> is empty for items that are not illustrations. This naming convention is a pre-requisite for using Batch Import so starting point for these post.

I see the following main scenarios for which I want to create different posts. This post can be used to discuss scenarios in general and other posts can be used for details about a specific scenario:

1. Import of translations
2. Updating a batch of items that do already (all) exist in the repository
3. Importing illustration items that do not exist in the repository
4. Importing XML items that do not exist in the repository

For import of translations I refer to the on-line documentation (TD14SP2): https://docs.sdl.com/LiveContent/content/en-US/SDL%20Tridion%20Docs-v2.1.2/GUID-ADB2096C-FEF7-469A-84E1-625752672BD2