Setup > Usage > Imports / exports > Sequences 

An import/export sequence is used to define using a single code, a group of templates with associated file paths. The advantage of these import/export sequences is to be able, at one go, to extract or integrate all the files defined in the database by using the templates listed in the sequence, in the order of the description.

In addition, when it is used sequentially, the export with chronological number is made with a single increment in the chronological number: There is therefore a coherence between exported data with respect to time.

The definition of the sequences is particularly useful when multiple imports/exports are automated using the batch server (a batch task launch import or export sequence exists).


SEEREFERTTO Refer to documentation Implementation

Screen management

The entry of a template is made using a single tab.

Entry screen


Firstly a sequence code is defined, then the different template codes to be used are entered, along with the corresponding file paths. These file paths may include the # character used during the chronological imports/exports.




The following fields are present on this tab :

Block number 1

  • Code (field CODE)

This code groups the various templates used for import-export.

  • Title (field DES)

Destined notably to figure in the reports and the screens in which the record code can be entered or selected. This text is used to give a clear description to the record concerned.


  • No. (field NUMLIG)


Code for template import-export existing.

  • Data file (field CHEMIN)

This is the access path to the file to be imported or exported.



Menu Bar

This is used to copy a sequence to another folder.

Menu Bar

Options / Export XML

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

Import/export templates: Record XXX does not exist

The template code that has been entered does not exist.

Note :

No directory existence test is made on the file path defined by default in the sequence (the directory may not yet exist: this test is only made on launching an import or export).

Tables used

SEEREFERTTO Refer to documentation Implementation