Definition of context to import events

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

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

Specify the characteristics of the import into the tabs.

Source Tab

The import source, which must be unique, can be a:

Depending on the selected type, settings are different.

Database case

If the import is from a Database, select the Database type.

Precise following settings:


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:


To validate these settings:

  • Click on OK
  • or Click on Cancel to undo the modifications.


The name of the database for import may be precised.


Select the name of the Table or the View to be imported.

This list is empty if the database is not specified.

SQL condition

It is possible to specify a SQL condition for particular filter the data to import.

This condition depends only on the structure of the outer table used as source.

Excel file case

Then define:


Select Excel file.


This is the path to the source file in *.XLS or *.XLSX.


This is the sheet from the source file to import.

CSV file case

Then define:


Select Csv file.


The Separator of the values in the source 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 file (CSV),
  • An URL path,
  • A text Export=NomDuContextImport which is used in exports from imports.

Specific values case

This allows you to import without the need for source file.

The import values ​​are defined directly in the import context.

This type of import is particularly suitable for the functionality of auto assignment.

Correspondence tab

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

This correspondance is done field by field.

Fill in the table that contains several columns:


This column contains the field and attributes names selected for import.

By clicking on , it allows you to import:

  • The General settings of each event,
  • Each heading of each dimension,
  • Each resource name, (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 import,
  • Each heading of each form,
  • Fixed and variable value, and coefficient of each valuation item,
  • The Internal Identifier (UID) of events.

If an operation heading is selected, the column Key will be automatically checked.


For each property or heading to import, select the source field in the list. The name of the source field and the destination heading can be different. This correspondence is done for each entry of the source file (or table).

The headings that has no correspondence works as following:

  • In case of new event insertion, the value of the heading is empty,
  • In case of existing event modification (by using a key), the value is not modified.


If the information does not come from the source, it is possible to enter the value of some fields manually through this column. This field value is the same for all imported events.

Special cases:

Global variables

In a text heading, it is possible to assign $USERNAME as an import value.

The value is the login of the user running the import.

cf. Triggers for Import/Export


In a heading or property as date, it is possible to set the launching date (“Now”) as the value of the date to be imported.

To do this, check the box on the right.

Multiple values

The insertion of multiple values ​​is possible in the following heading types:

To import multiple values, the values in the data source must be separated by the | character.

Auto assignment

In the case of specific values​​, it is possible to perform automatic assignment of resources to existing events. (cf. Assignment)

For the name of the dimension, the following window appears :

Three informations can then be indicated:


If this information is checked events are allocated according to sort headings in a ascendant way.

Sort heading

Select headings that define the criteria of automatic assignment.

Resources filter

This filter allows to define resources that can be assigned to events.


For each entry of the source file (or table), it is possible to verify if it already exists in the planner.

A key is a unique identifier consisting of one or more properties. It allows to make the difference between an insertion or an update.

Two cases are possible:

  • If any heading is defined as a key, it is an insertion of new events,
  • If one or several headings are defined as a key, it is an update of existing events and eventually an insertion of new events.

cf. Import mode

Parent Key

This feature requires at least one vertical hierarchy (cf. Events hierarchy)

For each entry found in the import source, it is possible to check whether the event-father already exists as an event in the schedule with this key concept.

Parent key allows you to find the event father for createing or updating events-son.

If the event-father does not exist, then his event-son can not be imported or updated.

Definition tab

Date format

Choose the format in which the dates will be set when importing.

Import mode

Three types of import are possible:

  • Creation only: consists in a simple insertion of events;
  • Modify only: with the definition of keys, it permits to update the events that are identified;
  • Modify/Creation: with the definition of keys, it permits to update the existing events and to create new ones.

Events filter

Specify what events are considered as present in the schedule. (Import for modification)

To do this, you must choose a Events Filter.

This filter is particularly useful when updating existing events.

Stored procedure

These parameter is only accessible if the import is done from 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

1) DataBase Management System
Translations of this page: