Definition of context to export events

This page describes required parameters for definition of Export Events context.

The parameters of others types of import/export context are available on:

Specify the characteristics of the export.

Destination Tab

The destination of the export can be:

According to the selected type, the required settings for the export are different.

Database case

If the destination of the export is a database, choose Database type.

Then define:


Select Database.


The type of DBMS1) has to be defined among:

  • MYSQL,

c.f. plannings_et_bases_de_donnees

Connection settings

The Connection settings are different depending on the DBMS type selected.

When defining the connection settings, a new window appears:


If the MSACCESS file does not exist yet, it is created when exporting.

To validate these settings:

  • Click on OK
  • or Click on Cancel to turn back.


The name of the database for export may be precised.


Select the name of the Table where to export.

This list is empty if the database is not specified.

Excel file case

Then define:


Select Excel file.


This is the path to the destination file in *.XLS or *.XLSX. If this file does not exist, it is created when exporting.


This is the sheet of the destination file where the data must be exported. If this sheet does not exist, it is created when exporting.

CSV file case

Then define:


Select Csv file.


The Separator of the values in the destination file that can be a:

  • Semicolon,
  • Dot,
  • Blank,
  • Coma,
  • or a Tab.


Select the encoding type according to the server operating system:

  • Default (System encoding)
  • UTF8
  • Windows-1252 (Windows)


The path could be :

  • A destination file (CSV). If the file does not exist, it is created when exporting,
  • An URL path,
  • A text Import=NomDuContextExport which is used in imports from exports.

Correspondence Tab

This tab establishes the correspondence between the source (events on the planner) and the destination (file, sheet or table).

This correspondence is done field by field.

Fill in the table that contains several columns:


This column contains the field and properties names selected for export.

By clicking on , it allows you to export:

  • The global properties of the event,
  • Each heading of each dimension,
  • Each resource of the event (cf. Identification headings),
  • Several headings in one time when the user click on (Select attributs). It could be useful when a large number of heading is concerned in the export,
  • Each heading of each form,
  • Fixed and variable value, and coefficient of each valuation item,
  • The Internal Identifier (UID) of ressources.

On calculated headings, only the persistents can be exported.


Choose for each property or heading to be exported the corresponding destination field. If no destination is selected, the property or heading is not exported.

  • In file case, the default name is the heading name. However, the name can be modified.
  • In table case, names may be selected from the list of fields in the destination table.


To export to a database table, it is possible to select a key by checking one or several Key? checkboxes.

cf. Add if no match

In the case of an export to a file, it is possible to set the order of columns in the export file using the arrows .

This order also defines the order of the resources in the file.

Definition Tab

Add if no match

These parameter is only accessible if the import is done from a Database (except MSACCESS).

In the database case, the export is by default inserting new data.

This box allows you to check in the database if the data destination already exists, and create only if it does not exist.

The key used for this verification is defined in correspondence tab.

Date format

Select the format of the dates to export:

  • dd/MM/yyyy
  • yyyy-MM-dd
  • MM/dd/yyyy
  • dd.MM.yyyy


It is possible to limit the export to some events. Therefore, select an events filter.


Select the Time Period in which the events to be exported are.

Type of intersection

Select the intersection of the events with the time period. The possibilities are:

  • Intersect the period,
  • Cover the period,
  • Included in the period,
  • Start in the period,
  • End in the period.

Stored procedure

These parameter is only accessible if the export is done to a Database (except MSACCESS).

Define the name of a stored procedure.

The stored procedures must have the two following features:

  • retcode equals to OUT and has INTEGER type: must have the value 0 if successful,
  • message equals to OUT and has VARCHAR type: must contains an explanatory text for the user.

cf. Context to follow

Import context to follow

These parameter is only accessible if the export is done to a Database (except MSACCESS).

This allows to launch another import context after the stored procedure is executed.

You must choose an import context from those available in the list.

The available import have only one of these types :

1) DataBase Management System
Translations of this page: