| Sv translation |
|---|
|
IntroductionImport Export Schemes are designed to replace the fixed import / export file structure in the jtel system. They work on CSV style files which are separated by a fixed character (usually but not always semicolon). Import export schemes require CSV files with a header line to work correctly. The import / export schemes mechanism provides a flexible way to specify: - the fields used in the data import process
- how they are formatted
- which internal field in the jtel system should the external field be mapped to
- the fields used in the export process
- which internal field in the jtel system should be mapped to a particular position in the export file
- how should it be formatted
Import export schemes provide a way to implement "asymetric" imports and exports - i.e. where the internal fields in the jtel system do not necessarily have to be mapped to data in the external file and vice versa, and the ordering of the fields can be implemented in a more flexible manner. Supported DataCurrently, import export schemes are supported by the following modules in the software: This feature set will be expanded in the future, and eventually the old import / export mechanism will be replaced by it entirely. ImportingWhen Data is imported, if it is too long for a field of type VARCHAR, it will be truncated. Creating / EditingImport export schemes are created using a client administrator account, and accessing the "System Settings ... Import Export Schemes" menu. The following information is required: | Field | Contents |
|---|
| Name | A name for the import export scheme. | | Import Export Name | The jtel internal data set on which this operation will operate. | | XML Definition | The XML definition for the import / export provided. |
XML DefinitionAn XML example definition is provided below, together with an example file, to illustrate the XML definition. | Translations Ignore |
|---|
| Code Block |
|---|
| title | Example XML Definition |
|---|
| <importExport2>
<import>
<type>CSV</type>
<encoding>UTF-8</encoding>
<delimiter>;</delimiter>
</import>
<export>
<type>CSV</type>
<encoding>UTF-8</encoding>
<bom>1</bom>
<delimiter>;</delimiter>
</export>
<fieldMappings>
<fieldMapping internalField="RandomSortOrder" externalField="Priority" externalType="INTEGER" importOnly="true"/>
<fieldMapping internalField="ReferenceNumber" externalField="RefNumber" externalType="VARCHAR"/>
<fieldMapping internalField="ExternalSystemLink" externalField="Hyperlink" externalType="VARCHAR"/>
<fieldMapping internalField="" externalField="EKCODE" externalType="VARCHAR"/>
<fieldMapping internalField="Salutation" externalField="Sal" externalType="VARCHAR"/>
<fieldMapping internalField="Name" externalField="Name" externalType="VARCHAR"/>
<fieldMapping internalField="FirstName" externalField="First" externalType="VARCHAR"/>
<fieldMapping internalField="Address" externalField="Addr" externalType="VARCHAR"/>
<fieldMapping internalField="Country" externalField="Country" externalType="VARCHAR"/>
<fieldMapping internalField="PostalCode" externalField="PostCode" externalType="VARCHAR"/>
<fieldMapping internalField="City" externalField="City" externalType="VARCHAR"/>
<fieldMapping internalField="PhoneNumber1" externalField="Tel1" externalType="TEL:49"/>
<fieldMapping internalField="PhoneNumber2" externalField="Tel2" externalType="TEL:49"/>
<fieldMapping internalField="Email" externalField="Mail" externalType="VARCHAR"/>
<fieldMapping internalField="Tag" externalField="DataIdentifier" externalType="VARCHAR"/>
<fieldMapping internalField="UserData" externalField="CustomerNumber" externalType="VARCHAR"/>
<fieldMapping internalField="dtBeginDate" externalField="StartDate" externalType="DATETIME:dd.MM.yyyy"/>
<fieldMapping internalField="dtEndDate" externalField="EndDate" externalType="DATETIME:yyyyMMdd"/>
<fieldMapping internalField="Client" externalField="ClientName" externalType="VARCHAR"/>
<fieldMapping internalField="" externalField="NotImported1" externalType="VARCHAR"/>
<fieldMapping internalField="" externalField="NotImported2" externalType="VARCHAR"/>
<fieldMapping internalField="" externalField="NotImported2" externalType="VARCHAR"/>
</fieldMappings>
</importExport2>
|
|
|
| Sv translation |
|---|
|
IntroductionEinführungImport Export Schemes are designed to replace the fixed import / export file structure in the jtel system. They work on CSV style files which are separated by a fixed character (usually but not always semicolon). Import export schemes require CSV files with a header line to work correctly. The import / export schemes mechanism provides a flexible way to specify: - the fields used in the data import process
- how they are formatted
- which internal field in the jtel system should the external field be mapped to
- the fields used in the export process
- which internal field in the jtel system should be mapped to a particular position in the export file
- how should it be formatted
Import export schemes provide a way to implement "asymetric" imports and exports - i.e. where the internal fields in the jtel system do not necessarily have to be mapped to data in the external file and vice versa, and the ordering of the fields can be implemented in a more flexible manner. Supported DataCurrently, import export schemes are supported by the following modules in the software: This feature set will be expanded in the future, and eventually the old import / export mechanism will be replaced by it entirely. ImportingWhen Data is imported, if it is too long for a field of type VARCHAR, it will be truncated. Creating / EditingImport export schemes are created using a client administrator account, and accessing the "System Settings ... Import Export Schemes" menu. The following information is required: |
| Field | Contents |
|---|
| Name | A name for the import export scheme. |
| Import Export Name | The jtel internal data set on which this operation will operate. |
| XML Definition | The XML definition for the import / export provided. |
-Export-Schemata sollen die feste Import/Export-Dateistruktur im Jtel-System ersetzen.
Sie arbeiten mit Dateien im CSV-Stil, die durch ein festes Zeichen (normalerweise, aber nicht immer Semikolon) getrennt sind. Import-Export-Schemata benötigen CSV-Dateien mit einer Kopfzeile, um korrekt zu funktionieren.
Der Mechanismus der Import-/Exportschemata bietet eine flexible Möglichkeit zur Spezifizierung:
- die im Datenimportprozess verwendeten Felder
- wie sie formatiert sind
- auf welches interne Feld im Jtel-System das externe Feld abgebildet werden soll
- die im Exportprozess verwendeten Felder
- welches interne Feld im Jtel-System auf eine bestimmte Position in der Exportdatei gemappt werden soll
- wie es formatiert sein sollte
Import-Export-Schemata bieten eine Möglichkeit, "asymmetrische" Importe und Exporte zu implementieren - d.h. bei denen die internen Felder im Jtel-System nicht notwendigerweise auf Daten in der externen Datei und umgekehrt abgebildet werden müssen und die Anordnung der Felder flexibler umgesetzt werden kann.
Unterstützte Daten
Derzeit werden Import-Export-Schemata von den folgenden Modulen in der Software unterstützt:
Dieser Funktionsumfang wird in Zukunft erweitert werden, und schließlich wird der alte Import-/Export-Mechanismus vollständig durch diesen ersetzt werden.
Importieren
Wenn Daten beim Import zu lang für ein Feld vom Typ VARCHAR sind, werden sie gekürzt.
Erstellen/Bearbeiten
Import-Export-Schemata werden unter Verwendung eines Client-Administrator-Kontos und unter Zugriff auf die "Systemeinstellungen ... Import-Export-Schemata" aufgerufen und erstellt..
Die folgenden Informationen sind erforderlich:
| Feld | Inhalt |
|---|
| Name | Ein Name für das Import-Export-Schema. |
| Import Export Name | Der interne Jtel-Datensatz, mit dem diese Operation durchgeführt wird. |
| XML Definition | Die XML-Definition für den Import/Export wird zur Verfügung gestellt. |
XML Definition
Nachstehend finden Sie eine XML-Beispieldefinition zusammen mit einer Beispieldatei, um die XML-Definition zu veranschaulichen
XML Definition
An XML example definition is provided below, together with an example file, to illustrate the XML definition.
| Translations Ignore |
|---|
| Code Block |
|---|
| title | Example XML Definition |
|---|
| <importExport2>
<import>
<type>CSV</type>
<encoding>UTF-8</encoding>
<delimiter>;</delimiter>
</import>
<export>
<type>CSV</type>
<encoding>UTF-8</encoding>
<bom>1</bom>
<delimiter>;</delimiter>
</export>
<fieldMappings>
<fieldMapping internalField="RandomSortOrder" externalField="Priority" externalType="INTEGER" importOnly="true"/>
<fieldMapping internalField="ReferenceNumber" externalField="RefNumber" externalType="VARCHAR"/>
<fieldMapping internalField="ExternalSystemLink" externalField="Hyperlink" externalType="VARCHAR"/>
<fieldMapping internalField="" externalField="EKCODE" externalType="VARCHAR"/>
<fieldMapping internalField="Salutation" externalField="Sal" externalType="VARCHAR"/>
<fieldMapping internalField="Name" externalField="Name" externalType="VARCHAR"/>
<fieldMapping internalField="FirstName" externalField="First" externalType="VARCHAR"/>
<fieldMapping internalField="Address" externalField="Addr" externalType="VARCHAR"/>
<fieldMapping internalField="Country" externalField="Country" externalType="VARCHAR"/>
<fieldMapping internalField="PostalCode" externalField="PostCode" externalType="VARCHAR"/>
<fieldMapping internalField="City" externalField="City" externalType="VARCHAR"/>
<fieldMapping internalField="PhoneNumber1" externalField="Tel1" externalType="TEL:49"/>
<fieldMapping internalField="PhoneNumber2" externalField="Tel2" externalType="TEL:49"/>
<fieldMapping internalField="Email" externalField="Mail" externalType="VARCHAR"/>
<fieldMapping internalField="Tag" externalField="DataIdentifier" externalType="VARCHAR"/>
<fieldMapping internalField="UserData" externalField="CustomerNumber" externalType="VARCHAR"/>
<fieldMapping internalField="dtBeginDate" externalField="StartDate" externalType="DATETIME:dd.MM.yyyy"/>
<fieldMapping internalField="dtEndDate" externalField="EndDate" externalType="DATETIME:yyyyMMdd"/>
<fieldMapping internalField="Client" externalField="ClientName" externalType="VARCHAR"/>
<fieldMapping internalField="" externalField="NotImported1" externalType="VARCHAR"/>
<fieldMapping internalField="" externalField="NotImported2" externalType="VARCHAR"/>
<fieldMapping internalField="" externalField="NotImported2" externalType="VARCHAR"/>
</fieldMappings>
</importExport2>
|
|
