This is an old revision of the document!
Table of Contents
Generic configuration of customer- and configurationItemImport
Configuration of CSV-PreProcessor
In Version 5.5.0.0 the preprocessor has been redesigned. Company- and contact person data are in one single file. Furthermore it is possible to import customAttributes.
Sample data:
- import.csv CSV-File.
- template.xml Template-XML, defines the XML-Format-files structure.
Sample configuration:
<preProcessorSettings encoding="UTF-8" key="default" delimiter=";" sourceDirectory="ConfigurationItemImport\preProcessDir" fileMask="*.csv" templateFilePath="ConfigurationItemImport\format.xml" useHeaders="true" />
encoding: The Encoding of the csv file. “Unicode” or “UTF-8” possible.
delimiter: Das separator of the values.
sourceDirectory: The folder, from which the files are imported.
fileMask: A filter, to allow just “*.csv” files.
templateFilePath: A Template-XML-File.
useHeaders: Defines if column headers are used (in the template file) othewise the culumns are named as following: column1, column2, columnN, …
Field mapping on XML-Import
All field values can be modified before saving the data on importing an xml-file.
Configuration
The mapping can be configured via database table “tbImportMapping”. The table has the following structure:
| Fieldname | Function |
|---|---|
| importName | The name of the import. e.g. “CustomerImport” or “ConfigurationItemImport” |
| fieldName | The name of the field. (see below) |
| currentValue | The fields current value. |
| nextValue | The fields new value. |
How to create a correct FieldNames
The “fieldName” is structured like the xml document.
Exception: The XML-Node “contactperson” is named “CustomerContactPerson”.
Examples:
CustomerContactPerson.attributes.test CustomerContactPerson.name status
