CSV export form

You can open the form for the CSV export via the Administration/Tools/Data exchange/CSV export menu.

Name (ID)

In addition to giving the data record its name, this field also acts as the record ID. Therefore, the entered character string must not contain any space characters.

Codepage

Selects the code page to be used (default: “Windows 1252”). If no entry is selected, the default is applied.

Attention

Attention: In order to use the right character set for the CSV export and to correctly convert all characters from the list, the Code page must be specified. In the selection menu, the system offers all code pages known to the server. These are not managed and depend on the Java runtime version installed. If the CSV file is created on a Windows system, the code p­age is most likely Windows 1252. The administrator can specify the standard code page for the CSV import by means of the PSA_COD_PAG_DEF environment variable.

Filters

Filters to be applied to the basic object. In the field selection menu, always all defined filters are offered.

Note: For objects with different classes, filters always need to be created for the base object. So, for example, always create contact filters in the contact overview list and mark them for the respective class (person or company in "all fields").

Separators

Separator between the individual columns (default: “;”).

1:n separator

This is used as the separator with 1:n relations. This way, several pieces of data can be placed into one column.

Quotation marks

Quotation marks of the cells (default: "). Quotation marks inside character strings must be doubled.

Sublist export fields

You can provide the actual definition of the CSV export in this sublist.

Position

The order in which the fields are defined.

Data class

In the first row of the field, enter the start data class of the CSV export. If a Filter is created in the header area, it accesses the start data class.

Field

Entry of the data class, which of its fields should be output. Here, you can also specify component fields.

CSV position

The column of the CSV export file in which the displayed field should finally appear. Do not confuse the order here with the Position column of the fields.

Header

Provides a header that can be specified in the first row of the export file. A header row that contains the specified header and defines the type in the first column, is always generated.

On the right-hand side of the specified data class, all its fields or components that should be output are listed.

1:n separator

If the data class is to be changed, the new data class, which from now on applies to all fields following this data class, should be specified in the Data class column after the last entry of the Field column of the preceding data class. They directly link to basic classes or to relations of the source object. The decisive factor is where the field is found from which the data is to be exported.

Link

Specifies which field from the new data class is to be encoded with which field of the pre­ceding data class. Convention: new DATACLASS.FIELD = old DATACLASS.FIELD. Several fields can be specified, separated by commas.

If you want to specify a fixed value for the encryption, put this value in single quotation marks, e.g., new DATACLASS.FIELD = 'FIXEDVALUE'.

Parent position

Position of the data class referred to. This way, it is possible to branch to other DTOs. For this, enter the number of the position to be opened virtually for the export. The relation is always backwards in sequence.

Using locales

As a default, the export uses the specified format, i.e. the code page. But, within the field definition, you can also use so-called Locales. The Locale class represents a set of country- and language-specific set­tings, e.g., the name of a country and the language. A locale object is always defined by three abbrevia­tions: for the country, the language and optionally for a variant. For this, the field name must be separated from the following locales by a vertical line (pipe).

Example convention: LST_PRI|L=N, de, DE

L corresponds to the locale definition.
N corresponds to the type (number).

The following types are currently available: N (Number), C (Currency), P (Percent).
Language (de) and country (DE) follow.

Using functions

Functions can also be used within field definitions. During an export, the data in the field is transformed using the specified function. For example, a date field can be exported in a human-readable format.

Example: BEG_DAT|F=de.pisa.psa.csv.CSVfnc.fmtLocDatSht

F corresponds to the function definition.
de.pisa.psa.csv.CSVfnc.fmtLocDatSht is the function that transforms a date field into the format <DD.MM.YYYY>.

Additional functions available in the CRM standard

de.pisa.psa.csv.CSVfnc.addBlk adds a leading space.
de.pisa.psa.csv.CSVfnc.addNul adds a leading zero.
de.pisa.psa.csv.CSVfnc.fmtNoc converts empty entries to "keine Angabe".
de.pisa.psa.csv.CSVfnc.fmtMon replaces "," with ".".
de.pisa.psa.csv.CSVfnc.fmtDat changes the date format to <DD.MM.YYYY HH:mm>.
de.pisa.psa.csv.CSVfnc.fmtLocDat changes the date format to <DD.MM.YYYY HH:mm> in local client time.
de.pisa.psa.csv.CSVfnc.fmtLocDatSht changes the date format to <DD.MM.YYYY> in local client time.
de.pisa.psa.csv.CSVfnc.fmtLog converts entries in logical fields to "ja" and "nein".
de.pisa.psa.csv.CSVfnc.fmtFldFmt changes the date format to the format specified in the field definition.

Component fields

The names in the person mask or the address field are fields that are formed by several components. The basic class must always precede the field name. Examples:

Address: PSA_ADR.CMP_ADR
Composite name (person): PSA_PRS.CMP_NAM
Composite name (company): PSA_ORG.CMP_NAM