Definition of context to import resources

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

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

Specify the features of the import into the existing tabs.

Source tab

The unique source of the import can be:

According to the selected type, the required settings for the import may be 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 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.

Correspondence tab

This tab establishes the correspondence between the source (dimension 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 attributes names selected for import.

By clicking on , it allows you to import:

  • Each heading of the dimension,
  • 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,
  • The Internal Identifier (UID) of ressources.

The following headings can not be imported:

  • Control column,
  • Operation,
  • GeoLocation (If Automatic location is checked),
  • and Event value.

If these headings are selected, the column Key will be automatically checked.


For each heading to import, select the corresponding source field in the list that appears. 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 heading that has no correspondence works as following:

  • In case of new resource insertion, the value of the heading is empty,
  • In case of existing resource 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 resources.

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 date heading, 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.


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 headings. It allows to make the difference between an insertion or an update.

Two cases are possible:

  • If any heading is checked as a key, it is an insertion of new resources,
  • If one or several headings are checked as keys, it is an insertion of new resources or eventually an update of existing resources.

cf. Import mode

Definition tab

The definition tab contains several types of features :

Resources settings

These informations are useful in case of an insertion of new resources (no key). These informations will be set for the new imported resources.

Existing resources are not modified.

Resources filter

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

To do this, you must choose a resources filter.

This filter is particularly useful when updating existing resources.

Import mode

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

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

Event import context

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