Skip to main content
Skip table of contents

CURSOR Importer

Installation documentation

General information

The CURSOR Importer is an optional software program that requires separate licensing.

  • The latest version is always delivered

  • Imported is configured via the configuration.bat file (You can change the language of thed interface here. Currently English and German are supported.)

  • Imported is started via the run.bat file
    The run.bat refers to a Java Runtime Environment in the folder of the importer. This should be in the jre folder. If this is not included, a JRE is searched for under Program Files (x86)\Java\<suitable jre version>\. If nothing is installed there either, the Importer will not start. In this case, download the JRE <suitable jre version> from the official site and create the jre subfolder for the importer.

  • The run_cmd.bat file can be used to start the import of one or more already created XML import files. For this purpose, the corresponding settings must be set in the configuration.bat.

Installation at the customer's site

  • The files to be delivered are located at  f:\Install\Java\KopiervorlageFuerAuslieferung\CURSOR Importer\<CRM Main Version>\<CRM Patch Version>. This includes the tool and the default settings.

  • The sample data can also be copied from the folder f:\Inhaus\Text\900 Entwicklung\Importer\Beispieldaten\.

  • Installation at the customer's site is done by copying the contained files.

  • (Warnung) By default, there is a TrustStore "truststore_cursor.p12" in the main folder. This is to be replaced by the client's TrustStore, which is also in the RichClient. To do this, the TrustStore is copied and specified in configuration.bat. Otherwise, access via the WebService is not possible.

Call as external call

If desired, the tool can also be started by an external call (of EXE type), in which the command refers to the run.bat.

Using templates

Currently there are three templates for the import of activities, business partners and products. These templates are delivered with example files as a guide.

The structure is designed in such a way that there is one folder for each template, which contains example source data (*_Import.csv), a suitable configuration file (*_conf.xxic) and a template (*_template.xml).

Available templates:

  • ACT_template.xml
    This template generates activities that are delegated to employees and populates the contained fields. Further relations such as contact persons are not populated.

  • GP_template.xml
    This template generates business partners with underlying person and default contact person, plus a street address and phone number.

  • PRD_template.xml
    This template generates products including a German product description.

In all cases, make sure that the source data contains valid keys from the target system. For example, Delegated to/from must be populated with a valid employee token. The same applies to the person type (PersontypeKey), where a valid key must be stored. If the keys in the sample data have been checked (usually the fields ending in Key), the import can be tested with the attached data.

Technical description

The CURSOR Importer is an optional software program that requires separate licensing.

The CURSOR Importer is an interface for importing data from CSV files or Excel tables (referred to as 'source data file' below). Using this interface, a user with the appropriate previous knowledge should be able to import data of a defined data structure independently. No in-depth knowledge of the data model or application is required.

XML templates are available to make it as easy as possible for the user to use, with each template guaranteeing the import of one defined data structure. The templates are provided by CURSOR Software AG and their functional scope is described.

The user receives a configuration file (*.xxic) and a template file (*.xml) that describes the structure of the source data file. Using this configuration, the customer can process multiple source data files of the same structure. The first step is to generate XML data for the XML import interface using CSV or Excel tables. In a second step, the CURSOR Importer enables direct import of data via the web service interface.

The Importer then configures which information from the source file is to be transferred to which information in the target file. This presupposes that the two structures fit together. If this is not the case, the templates must be adapted.

As a rule, further checks must be taken into account in an import scenario. This includes, for example, a check for duplicates or a consistency check of the data; this is not part of the Importer, but must be taken into account in the scenario with separate tools or procedures.

Features for users

When using the tool, it is recommended to split the procedure into two steps:

  1. Initial setup with CURSOR Software AG (settings of import parameters)

  2. Independent execution of the import

The settings of the import parameters remain as last-run settings in the lastrun.properties file. For further import processes, it is then only necessary to select the new source data file.

All steps necessary for using the tool are described below; since the settings are saved, this is only necessary for the initial configuration. Especially with the points described under 'Settings for the web service import', later changes are usually not necessary.

Setting up a project

Loading the source data file

  • Click the Browse button to open a search dialog.

  • Select your file with the data to be imported in the search dialog.

Selecting the table (Excel files only)

If you have selected an Excel file, it is imported. In the Table selection box, select the table containing the data you want to import.

Settings

If you have selected a CSV or Excel file, you can use the Settings button to select the separators and text separators used in the file, the escape character, the character set used (all CSV only) and a date format. If the dialog is not opened, the values are preset. Most of the time these settings are already correct. The Default button can be used to reload the default settings.

The settings must correspond exactly to the coding in the source data file! Only the date format is optional, since the two default formats of the XML import interface are also supported.

CSV


Excel

Loading the configuration file

You have received a configuration file (*.xxic) from CURSOR Software AG. This describes the structure of your source data file.

  • Click the Browse button to open a search dialog.

  • Select the configuration file in the dialog.

Loading the template file

You have received a template file (*.xml) from CURSOR Software AG that serves as a template for the import instructions to be generated.

  • Click the Browse button to open a search dialog.

  • Select the template file in the dialog.

Selecting the output folder

To perform the import process, the import instructions must be stored in a directory.


If possible, select an empty directory or create a new one.

Choosing the prefix

Output files are created according to the <My prefix>_000000000001.xml format. The prefix can be chosen freely here. Only characters that are not allowed in the operating system's file system are excluded.

Setting the offsets

If the data to be imported is offset in the file selected above (i.e. does not start in column 1, row 1), the offsets must be adjusted accordingly. If the first line of the data file (or Excel table) is a header line, the vertical offset must be set to 1. (In the example below, the data for the import starts at row 3, column 1)

Setting the Web Service Import

  • If you do not want to import directly via the web service but only want the XML output, skip this step. In this case, the XML files are saved in the predefined output folder.

  • The tool can also be used with the 'Websphere' application server, but no web service is currently supported.
    In this case, deactivate the 'Import via web service' option. Instead, the XML output folder can be set to the monitored client directory to continue with the client-side import.

  • Activate the Import via web service.

  • Adapt the URL for the web service to your server. The URL usually has the form:

http://<HOSTNAME>:<Portrange 1-5>8080/<PRODUCT NAME CARMEN/EVIJET/HELVIS>-ejb/WebServiceController


How to get to the address of the web service

1

Select the menu item Administration / Create system information.

2

An email is then automatically created. Search for the following content:

[...] WebClient URL: http://dailybuild.cursor.de:18080/EVIJET-webclient WebService Interface: http://dailybuild.cursor.de:18080/EVIJET-ejb/WebServiceController?wsdl Invocation Servlet: http://dailybuild.cursor.de:18080/EVIJET/invocation/InvocationServlet [...]

  • Enter the appropriate values for server, port range and product. For more details on web services, see the documentation for administrators (chapter web services).

  • Enter a user name and password. The user should have authorization to access the web services in your system.

Test run and/or import

The actual import takes place after a test run as standard. If the configuration file proves to be faulty, the import is not started. This prevents the data from being imported only partially.

If the import worked without errors and there is an Excel table with the same structure, you can skip the test run to speed up the import process.

Packet size

The 'Packet size' parameter specifies the maximum number of datasets to be combined into one import statement. If the number is exceeded, a new XML file is created.

The default packet size of 800 is recommended. Significantly smaller or larger values can slow down the import.

Transaction time

The maximum time that the import of a packet (NOT the complete import) may take before it is rolled back can be set via 'Transaction time'. The minimum time is 5 minutes, the maximum 23 hours and 59 minutes.

Use stylesheet for result

Instead of

CODE
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

the web service result files now start with

CODE
<?xml-stylesheet href="file:///<Laufwerk>:/<Pfad>/Standard.css" type="text/css"?>

This allows the file to be opened and formatted with the browser, for example. If only the check mark is set, the path automatically points to the default.css in the Importer folder. If a stylesheet is specified in the text field, this path is set.

Execute/Cancel the import process

  • Start the import process using the Start button.

  • First, the XML import statements are generated from the source data file in the selected output directory. Usually, this conversion will only take a small amount of time.

  • If Import via web service was selected, a connection to the web service of the CRM server is then established and the data is imported in a test run or actual import. This process can take some time depending on the amount of data.

  • You can cancel the process by clicking Cancel. If the XML files are still being created, the process is aborted directly. If the web service call is already running, it is only terminated after the next call.

  • The time remaining until the end of the transaction is displayed at the bottom of the screen.

Save/load project

In the Project menu you can save your entries (e.g. source data file, configuration, offsets, web service settings) and restore them at a later time. This is useful if you want to import Excel tables and CSV files with different structures. The import parameters are saved in a project file (*.xprj).

1. First select Save project.

2. Select a location.

3. Later, select Open project.

4. And select the saved file.

Column assignment

The configuration file that assigns the columns of the source data file to the placeholders of the template file, can be created in the tool itself.

  • First, a source data file must have been loaded in the interface (see step Load source data file).

  • The column assignment input mask is accessed via the project menu.

Now a dialog for entering an offset appears. The default value is the offset set in the main dialog. This is also reset when you click on Default.


The difference between the two offsets

The offset in the main dialog must point to the beginning of the data to be imported. The offset required here should point to the values that identify the field particularly well. For example, if there is another row with headings above the data, you can set the offset to this row.

  • If a template file was previously selected, it is already preselected, otherwise it can be selected using Browse.

    The tool reads them in and lists the placeholders under 'Template key'.

  • The possible columns from the source data file are in the selection lists under "Data column". The line used is the one at the offset of the source data file set when the dialog is opened.

  • A column of the source data file is assigned to each template key.

  • The column assignment must be saved (Save, *.xxic) and then loaded as a configuration file in the main mask.

  • If you want to change it later, you can load and edit it by clicking Load.

  • Save Selection creates a copy of the selected template. This copy does not contain all fields, but only all fields that were assigned in the Data column. If the data in the source file is not always the same, you should first define a template with the superset of all fields. This button can then be used to quickly create a template that matches the existing data.

  • Assign automatically assigns the template key and the values from the selection list to each other if they are the same.

Find/Replace patterns

By specifying regular expressions, values from the source file can be reformatted before they are written to the XML structure. The syntax is:

CODE
<Mein Muster zum Suchen>,<Mein Muster zum ersetzen>

Examples:

XML
MeinText,Text
^(\d{2})\.(\d{2})\.(\d{4})$,$3-$2-$1
NULL,
d[a-z]*d,MeinNeuerWert

Further information can be found in the Oracle documentation: http://docs.oracle.com/javase/7/docs/api/java/util/regex/Pattern.html

Global settings

In the project menu, under Global settings, settings can be made that apply to all projects.

LogPath

You can select the directory to which you want to log. By default, this is the directory of the Importer itself.

Log files

The CURSOR Importer logs into different files. All types of files (described below) create a new file if they reach a certain size. Old files are retained until a certain number of files are present, then the oldest file is overwritten again.

  • errors.log

Real errors are logged here. For example, if the server is not running, a program error occurs and the wrong encoding has been specified for the source file. This should be the first port of call if the web service could not be called. The 'Show errors in log dialog' check mark determines whether this file is loaded and displayed in the log dialog.

  • warnings.log

Warnings are logged here. For example, if the lastrun.properties was not found. This is not an error, since the default values are then used. Normally this file will not be of interest to the user. The 'Show warnings in log dialog' check mark determines whether this file is loaded and displayed in the log dialog.

  • progress.log

All activities of the Importer are logged here. For example, replacing the variables, reading in the values, etc. Normally this file will not be of interest to the user. The 'Show progress in log dialog' check mark determines whether this file is loaded and displayed in the log dialog.

  • webservice_input.log

The XML code sent to the web service is logged here. The 'Show web service input in log dialog' check mark determines whether this file is loaded and displayed in the log dialog.

  • webservice_output.log

The XML code received from the web service is logged here. This should be the first point of call if the server or web service has been reached but the desired result has not been achieved. The 'Show web service output in log dialog' check mark determines whether this file is loaded and displayed in the log dialog.

Number of files to load

Under 'Log files' it has already been described that old versions of any kind of file can still exist. The 'Load only the newest log file' option determines whether these are also loaded when opening the log dialog. This can make opening the dialog take a long time.

Show return dialog

If the web service is reached but an error is detected in the XML structure, the returned XML structure is displayed in a dialog. This can be turned off with the 'Process web service return' option.

Return dialog

If the web service is reached but an error is detected in the XML structure, the returned XML structure is displayed in a dialog.

  • The individual datasets can be selected in the tree on the left.

    • The errors contained in it are now displayed on the right-hand side.

  • The 'Only show errors' option filters out the datasets that have reported an error.

Log dialog

The View log files button can be used to view the contents of all files configured via the global settings.

Use the STRG+F key combination to open a search dialog on the tabs.

Batch mode

The CURSOR Importer allows operation in batch mode. The graphical user interface (GUI) is not used. Instead the settings are passed via command line parameters and the import process is started immediately. The following parameters are available:

Short form parameters

Long form parameters

Argument

Available since version

Description

-c

--config

<path>

3

The fully qualified path, or the path specified relative to the Importer folder, to the configuration file that is to be preset.

-d

--dest

<dir>

3

The fully qualified path, or the path specified relative to the Importer folder, to the directory in which the XML files are placed.

-df

--dateformat

<format>

145

The optionally additionally supported date format for CSV files. Default: yyyy-MM-dd'T'HH:mm:ss

-dp

--destprefix

<prefix>

694

The prefix for the generated XML files. Default: output

-e

--encoding

<encoding>

140

The encoding of the CSV file. Default: windows-1252

-es

--escape

<char>

140

The escape character of the CSV file. Default: \

-f

--source

<path>

3

The fully qualified path, or the path specified relative to the Importer folder, to the data file.

-h

--h-offset

<n>

3

The horizontal offset. Default: 0

-p

--packetsize

<n>

3

The number of datasets imported in one go. Default: 800

-pr

--project

<path>

215

The fully qualified path, or the path specified relative to the Importer folder, to the project file from which all values are read. If this parameter is set, all others are ignored.

-q

--quote

<char>

140

The text quotation marks of the CSV file. Default: “

-s

--sheet

<name>

3

The Excel table of the data file to be preselected.

-t

--template

<path>

632

The template file.

-sep

--separator

<char>

140

The separator of the CSV file. Default: ;

-v

--v-offset

<n>

3

The vertical offset. Default: 1

-us

--use-stylesheet

<1 / 0>

1261

Use a stylesheet to display the web service result. If the -ss option is not set, the default.css file in the main directory of the Importer is used.

-ss

--stylesheet

<path>

1261

Use this stylesheet to display the web service result. Only applies if the -us option is set.

-w

--webservice

<type>

3

After creating the XML, run the web service. Use the specified type (test, import, both)

-ws

--webservice-server

<server>

694

The server that provides the web service. Alternatively, -wu can be used.

-wp

--webservice-product

<product>

694

The CURSOR product to be addressed (CARMEN/EVIJET/INHOUSE/HELVIS). Alternatively, -wu can be used.

-wr

--webservice-portrange

<portrange>

694

The set port range of the server. Alternatively, -wu can be used.


--webservice-password

<hash>

3

The encrypted password for logging in to the web service. Required when -w is used.

-wu

--webservice-url

<url>

3

The URL of the web service. Required when -w is used. Alternatively, -wr + -wp + -ws can be used.


--webservice-user

<user>

3

The user name for logging on to the web service. Required when -w is used.

To see the operating notes, the class de.cursor.importer.console.ConsoleImporter can be called without parameters:

For example, an import command might look like this (the command is wrapped to improve readability):

EXCEL

CODE
$java -cp importer.jar de.cursor.importer.console.ConsoleImporter
-c d:\ImporterBeispiele\Excelbeispiel\config.xxic -s Tabelle1 -d d:\ImporterBeispiele\Ausgabe
-f d:\ImporterBeispiele\Excelbeispiel\acts.xlsx -t d:\ImporterBeispiele\Excelbeispiel\template.xml
-v 1 -w both --webservice-url http://localhost:18080/CARMEN-ejb/WebServiceController
--webservice-password 7FC203845F060800D0CA152D46BA8269 --webservice-user bne
 
 
Mit SSL (ab 19.2 zwingen nötig):
$java -cp importer.jar -Djavax.net.ssl.trustStore="mytruststore.p12" -Djavax.net.ssl.trustStorePassword="mytruststorepw" de.cursor.importer.console.ConsoleImporter
-c d:\ImporterBeispiele\Excelbeispiel\config.xxic -s Tabelle1 -d d:\ImporterBeispiele\Ausgabe
-f d:\ImporterBeispiele\Excelbeispiel\acts.xlsx -t d:\ImporterBeispiele\Excelbeispiel\template.xml
-v 1 -w both --webservice-url http://localhost:18080/CARMEN-ejb/WebServiceController
--webservice-password 7FC203845F060800D0CA152D46BA8269 --webservice-user bne


Ab 21.1.1:
$java -cp lib/importer.jar -Djavax.net.ssl.trustStore="mytruststore.p12" -Djavax.net.ssl.trustStorePassword="mytruststorepw" de.cursor.importer.console.ConsoleImporter
-c d:\ImporterBeispiele\Excelbeispiel\config.xxic -s Tabelle1 -d d:\ImporterBeispiele\Ausgabe
-f d:\ImporterBeispiele\Excelbeispiel\acts.xlsx -t d:\ImporterBeispiele\Excelbeispiel\template.xml
-v 1 -w both --webservice-url http://localhost:18080/CARMEN-ejb/WebServiceController
--webservice-password 7FC203845F060800D0CA152D46BA8269 --webservice-user bne


CSV

CODE
$java -cp importer.jar de.cursor.importer.console.ConsoleImporter
-c d:\ImporterBeispiele\Aktivitäten\act_conf.xxic -t d:\ImporterBeispiele\Aktivitäten\ACT_template.xml
-d d:\ImporterBeispiele\Ausgabe -f d:\ImporterBeispiele\Aktivitäten\act_import.csv -v 1 -w both
--webservice-url http://localhost:18080/CARMEN-ejb/WebServiceController --webservice-password 7FC203845F060800D0CA152D46BA8269
--webservice-user bne -e windows-1252 -es \ -sep ; -q \" -df dd.MM.yyyy
 
 
Mit SSL (ab 19.2 zwingen nötig):
$java -cp importer.jar -Djavax.net.ssl.trustStore="mytruststore.p12" -Djavax.net.ssl.trustStorePassword="mytruststorepw" de.cursor.importer.console.ConsoleImporter
-c d:\ImporterBeispiele\Aktivitäten\act_conf.xxic -t d:\ImporterBeispiele\Aktivitäten\ACT_template.xml
-d d:\ImporterBeispiele\Ausgabe -f d:\ImporterBeispiele\Aktivitäten\act_import.csv -v 1 -w both
--webservice-url http://localhost:18080/CARMEN-ejb/WebServiceController --webservice-password 7FC203845F060800D0CA152D46BA8269
--webservice-user bne -e windows-1252 -es \ -sep ; -q \" -df dd.MM.yyyy


Ab 21.1.1:
$java -cp lib/importer.jar -Djavax.net.ssl.trustStore="mytruststore.p12" -Djavax.net.ssl.trustStorePassword="mytruststorepw" de.cursor.importer.console.ConsoleImporter
-c d:\ImporterBeispiele\Aktivitäten\act_conf.xxic -t d:\ImporterBeispiele\Aktivitäten\ACT_template.xml
-d d:\ImporterBeispiele\Ausgabe -f d:\ImporterBeispiele\Aktivitäten\act_import.csv -v 1 -w both
--webservice-url http://localhost:18080/CARMEN-ejb/WebServiceController --webservice-password 7FC203845F060800D0CA152D46BA8269
--webservice-user bne -e windows-1252 -es \ -sep ; -q \" -df dd.MM.yyyy

And the result would be:

To generate the password hash, use:

CODE
$ java -cp importer.jar de.cursor.importer.helper.PasswordStorage <Passwort>

Technical documentation

How to create a new project

If you do not yet have a configuration file for an existing template which you want to use to import an existing source file, proceed as follows:

  1. Select the source data file

  2. Select the Project/Column Assignment menu item

  3. Select the template file in the configuration dialog

  4. Configure the mapping accordingly

  5. Click on the Save column assignment button to create the configuration file.

If a row with headings was inserted above the first data row in the source file, it may be helpful to set the offset to the row with the headings before opening the configuration dialog. This makes it easier to assign meaningful headings.

Creating configuration files and template files

Step 1

First, an example template.xml file is created according to the XML import schema. The file contains only a single <Entry> tag, no XML declaration and no <Entries> root tag.

The file must have UTF-8 encoding but no byte order mark.

Example:

XML
 <Entry entity="Customer" action="UPDATE_OR_CREATE" found="ONE">
<Field name="MatchCode.Customer" identifyingField="true">
<FieldValue>
<stringValue>HELABA BANK</stringValue>
</FieldValue>
</Field>
 
<Field name="Name1.Customer" identifyingField="false">
<FieldValue>
<stringValue>Landesbank Hessen-Thüringen</stringValue>
</FieldValue>
</Field>
 
<Field name="Name2.Customer" identifyingField="false">
<FieldValue>
<stringValue>AG</stringValue>
</FieldValue>
</Field>
 
<Field name="Name3.Customer" identifyingField="false">
<FieldValue>
<stringValue />
</FieldValue>
</Field>
 
<Field name="PeAddressType.Customer" identifyingField="false">
<FieldValue>
<stringValue>STRASSE</stringValue>
</FieldValue>
</Field>
 
<Field name="PeStreet.Customer" identifyingField="false">
<FieldValue>
<stringValue>Ständeplatz</stringValue>
</FieldValue>
</Field>
 
<Field name="PeStreetNumber.Customer" identifyingField="false">
<FieldValue>
<stringValue>17</stringValue>
</FieldValue>
</Field>
 
<Field name="PeCity.Customer" identifyingField="false">
<FieldValue>
<stringValue>Offenbach</stringValue>
</FieldValue>
</Field>
 
<Field name="PeZIP.Customer" identifyingField="false">
<FieldValue>
<stringValue>34117</stringValue>
</FieldValue>
</Field>
 
<Field name="PhoneNoCountry.Customer" identifyingField="false">
<FieldValue>
<stringValue>+49</stringValue>
</FieldValue>
</Field>
 
<Field name="PhoneNoCity.Customer" identifyingField="false">
<FieldValue>
<stringValue>069</stringValue>
</FieldValue>
</Field>
 
<Field name="PhoneNoBase.Customer" identifyingField="false">
<FieldValue>
<stringValue>9132</stringValue>
</FieldValue>
</Field>
 
<Field name="PhoneNoExtension.Customer" identifyingField="false">
<FieldValue>
<stringValue>01</stringValue>
</FieldValue>
</Field>
 
<Field name="CustTypeKey.Customer" identifyingField="false">
<FieldValue>
<stringValue>KEINE BEZIEHUNG</stringValue>
</FieldValue>
</Field>
 
<Field name="EmployeeOffice.Customer" identifyingField="false">
<FieldValue>
<stringValue>ALA</stringValue>
</FieldValue>
</Field>
 
<Field name="EmployeeSales.Customer" identifyingField="false">
<FieldValue>
<stringValue>THR</stringValue>
</FieldValue>
</Field>
</Entry>

Step 2

The values of the fields of the above template file that are to be populated from the source data file during import are replaced by any placeholders. Placeholders have the form @$<PlaceholderID>$@. The placeholders are initially independent of the order of the columns in the source data file.

Example:

XML
 <Field name="Name1.Customer" identifyingField="false">
<FieldValue>
<stringValue>@$CustomerName$@</stringValue>
</FieldValue>
</Field>
<Field name="PhoneNoBase.Customer" identifyingField="false">
<FieldValue>
<stringValue>@$PhoneBase$@</stringValue>
</FieldValue>
</Field>

Fields that are to be assigned a fixed value during import remain unaffected.

Step 3

Now a configuration file config.xxic is created, which assigns the columns of the source data file to a placeholder in the template file. This can be done from within the program, as explained manually below.

The file is structured as follows:

  • each line contains an assignment: <key>=<value> starting with the key 0.

  • Mandatory key: template must specify the path to the template file created above (possibly relative to the configuration file itself).

  • A placeholder is assigned to each column index of the source data file: <Column index>=<placeholder>

  • In addition, each column can be assigned a processor class that allows virtually any checks and changes to the values. However, these changes only take effect after a value has been read in. For example, you cannot change a date value in this way so that it matches the specified date format.
    <Columnindex>.processors=<Class1>;<Class2>(<Arg1>,<Arg2>);..;<classN>

    • Possible processor classes are currently:

      1. NotEmpty -- Reports an error when a field of the column is empty

      2. Regex -- Performs a search/replace using regular expressions in each field of this column (see example below)

      3. IsFloat -- Reports an error if the value in the column is not a float

      4. IsInt -- Reports an error if the value in the column is not an integer

Example:

CODE
template=template.xml
0=CustomerName
1=PhoneBase
2=Date
2.processors=NotEmpty;Regex(^(\\d{2})\\.(\\d{2})\\.(\\d{4})$,$3-$2-$1)

This would mean that no empty values are allowed in the third column (Date), and values of the form DD.MM.YYYY are converted to YYYY-MM-DD.

Special features for number and date formatting

Excel

Number and date values from Excel are not transferred to the XML structure as specified in Excel, but an attempt is made to adapt them to the type specified in the template. For numbers with <intValue></intValue>, for example, decimal places would be trimmed, while with <doubleValue></doubleValue> or <longValue></longValue> they would be taken over, or filled up with zeros. Date values are converted to date with/without time. A list of the Excel formats for which this works correctly is given below.

Any formatting not listed here is not supported.

Supported number formats

In all cases, both point and comma are supported as pre/post decimal separators.

  • Numbers can be formatted as standard.

  • Numbers can be formatted as text.

  • If the numbers are formatted as number, all setting options may be used.

If a number ends with ".0" and the target is a <stringValue>, the ".0" is trimmed.

Supported date formats

  • If a date is formatted as date, all German and English (UK) formats can be used.

  • If a date already has the correct structure for the interface, in other words 1983-07-05T00:00:00 or 1983-07-05, it can also be formatted as standard or text. In this case, however, formatting is only done between these two formats, all other formats do not work here.

In addition, any other format is supported per Excel file. After loading an Excel file, a dialog can be opened using the Settings button, in which this format can be specified. This only applies if neither of the two default formats has been recognized.


Possible date configurations

Letter

Description

Example

G

Epoch

after Christ

y

Year

1996 or 96

M

Month in the year

February or Feb or 02

w

Week in the year

27

W

Week in the month

2

D

Day in the year

189

d

Day in the month

10

F

Day in the week of the year

2

E

Day in the week

Fr or Friday

a

AM/PM

PM

H

Hour of the day (0-23)

0

k

Hour of the day (1-24)

24

K

Hour in AM/PM (0-11)

0

h

Hour in AM/PM (1-12)

12

s

Minute in the hour

30

s

Second in the minute

55

S

Millisecond

978

z

General time zone

CEST

Z

RFC 822 time zone

+0200

Examples: "yyyy.MM.dd G HH:mm:ss z", "EEE, MMM d, yy", "h:mm a", "K:mm a, z", "yyyyy.MMMMM.dd GGG hh:mm aaa", "EEE, d MMM yyyy HH:mm:ss Z", "yyMMddHHmmssZ"

CSV

For number and date values from CSV, an attempt is made to adapt them to the type specified in the template. For numbers with <intValue></intValue>, for example, decimal places would be trimmed, while with <doubleValue></doubleValue> or <longValue></longValue> they would be taken over, or filled up with zeros. Date values are converted to date with/without time. A list of the formats for which this works correctly is given below.


Supported number formats

Numbers can be given as integers, separated by a period or comma.


Supported date formats

Date values can be specified in the two standard XML import formats. This is always checked first.

In addition, any other format is supported per CSV file. After loading a CSV file, a dialog can be opened using the

Settings button, in which this format can be specified. This only applies if neither of the two default formats has been recognized.


Possible date configurations

Letter

Description

Example

G

Epoch

after Christ

y

Year

1996 or 96

M

Month in the year

February or Feb or 02

w

Week in the year

27

W

Week in the month

2

D

Day in the year

189

d

Day in the month

10

F

Day in the week of the year

2

E

Day in the week

Fr or Friday

a

AM/PM

PM

H

Hour of the day (0-23)

0

k

Hour of the day (1-24)

24

K

Hour in AM/PM (0-11)

0

h

Hour in AM/PM (1-12)

12

s

Minute in the hour

30

s

Second in the minute

55

S

Millisecond

978

z

General time zone

CEST

Z

RFC 822 time zone

+0200

Examples: "yyyy.MM.dd G HH:mm:ss z", "EEE, MMM d, yy", "h:mm a", "K:mm a, z", "yyyyy.MMMMM.dd GGG hh:mm aaa", "EEE, d MMM yyyy HH:mm:ss Z", "yyMMddHHmmssZ"

Automatic filling with the blank key

If an import is to be performed via the CURSOR Importer or directly via the XML import interface, and a lookup field in which the blank key is allowed is not populated (see the following examples), it is now automatically populated with the blank key. These changes apply to versions 12.1, 11.2.01 and 11.1.14.

Example for Excel:

Example for CSV:

Example for XML:

Empty Boolean, Double, Date

If an import is to be performed via the CURSOR Importer and a date, number or Boolean field is not populated (see the following examples), it is now emptied.

Example for Excel

Example for CSV

Excel error: Unexpected characters in the text

If multi-line text is stored in a cell in an xlsx file, unexpected characters may appear at the position of the line break in the generated XML files and thus also in the imported datasets. For example "_x000D_". This is an Excel bug which CURSOR Software AG has no control over. As a workaround, the xlsx file can be saved as an xls file and re-imported by the Importer. This circumvents the problem.

CODE
$java -cp importer.jar de.cursor.importer.console.ConsoleImporter
-c d:\ImporterBeispiele\Aktivitäten\act_conf.xxic -t d:\ImporterBeispiele\Aktivitäten\ACT_template.xml
-d d:\ImporterBeispiele\Ausgabe -f d:\ImporterBeispiele\Aktivitäten\act_import.csv -v 1 -w both
--webservice-url http://localhost:18080/CARMEN-ejb/WebServiceController --webservice-password 7FC203845F060800D0CA152D46BA8269
--webservice-user bne -e windows-1252 -es \ -sep ; -q \" -df dd.MM.yyyy
 
 
Mit SSL (ab 19.2 zwingen nötig):
$java -cp importer.jar -Djavax.net.ssl.trustStore="mytruststore.p12" -Djavax.net.ssl.trustStorePassword="mytruststorepw" de.cursor.importer.console.ConsoleImporter
-c d:\ImporterBeispiele\Aktivitäten\act_conf.xxic -t d:\ImporterBeispiele\Aktivitäten\ACT_template.xml
-d d:\ImporterBeispiele\Ausgabe -f d:\ImporterBeispiele\Aktivitäten\act_import.csv -v 1 -w both
--webservice-url http://localhost:18080/CARMEN-ejb/WebServiceController --webservice-password 7FC203845F060800D0CA152D46BA8269
--webservice-user bne -e windows-1252 -es \ -sep ; -q \" -df dd.MM.yyyy

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.