File: Standard import of reporting counters values

Voir la version française

Object of the interface

The interface is used to import the values of the various counters calculated by a third party system at a given date. The objective is to make available the expected information in a text file that will be read and interpreted by the interface so as to update the database. It is possible to import unique, weekly or periodic values.

Learn more about setting up this import.

File name

The name of the file is free (label + extension) but once defined in the import settings, it should not change. It can contain information relating to one or more counters concerning one or more people.

Examples: Counters_A.txt, Counters_Timesquare.001, Counters.csv.

Format

Text. UTF-8 encoding.

Separator between two information

The separator between two pieces of information is the semicolon (;).

Description of the file content

Order	Field name	Type	Notes
01	Counter code	Alphanumerical	With no space or no special character
02	Identification of the employee concerned	Alphanumerical	With no space or no special character
03	Last update / Start date	Date	DD/MM/YYYY (day, month, year)
04	Counter value	Numerical	XXXXXXXXYY Can be interpreted as a number of hours, an integer or a real according to the nature* of the counter.
05	Start date	Date	DD/MM/YYYY (day, month, year), start date for periodic and weekly counters, empty for other counters
06	End date	Date	DD/MM/YYYY (day, month, year), end date for periodic and weekly counters, empty for other counters

Rules

* The nature of the counter is defined when it is created in Timesquare® and, depending on the case,
XXXXXXXXYY will be interpreted as: :

• An integer: YY always equal 00. 123 appears in the file as follows 12300.
• A real value: YY are the two decimals that represent the counter concerned. 526,98 appears in
  the file as follows 52698.
• A number of hours: YY represents the minutes and XXXXXXXX the hours. 122h38 appears in
  the file as follows 12238.

For unique values counters, the value date is equal to the counter last update date.

For weekly values counters, the value date must be the first day of the week. The end date can also be used as the end date for a weekly values counter relating to a partial week. Example: a partial AWD value.

For periodic values counters, the Start Date and End Date columns are used to indicate the period to which the value refers. In this case:

• If the value to be imported has no common period with the values ​​already present in the database, a new value is inserted into the database.
• If the value to be imported is exactly identical to a value already present in the database, a new value is inserted into the database, canceling and replacing the existing target value.
• If the value to be imported is included in an existing value, a new value is inserted into the database, canceling and replacing the existing value.
• If the value to be imported shares a common period with one or more existing values, then a new value is inserted into the database. It cancels and replaces the existing values ​​with a common period.
• If the value to be imported completely overlaps one or more existing values ​​without being identical to any of the existing values, then a new value is inserted into the database.
  It cancels and replaces the existing values ​​with a common period.

For weekly counters, the Start Date and End Date columns are used to indicate the period to which the value relates. This period is particularly necessary to handle partial DHR weeks, for example, at the beginning and end of the annualization period.

In this case:

• If the value to be imported has no common period with the values ​​already present in the
  database, then a new value is inserted into the database.
• If the value to be imported is strictly identical to a value already present in the
  database, then a new value is inserted into the database; it cancels and
  replaces the existing target value.
• If the value to be imported is included in an existing value, then a new value is
  inserted into the database. It cancels and replaces the existing value.
• If the value to be imported has a common period with one or more existing values,
  then a new value is inserted into the database. It cancels and replaces existing values ​​with a common period.
• If the value to be imported completely overlaps one or more existing values ​​without being identical to any of the existing values, then a new value is inserted into the database.
  It cancels and replaces the existing values ​​with a common period.

Example of content

File example (periodic reporting counter)

BRZCPACQ26;BRZ01;01/01/2026;178200;01/01/2026;31/12/2026;
BRZCPACQ26;BRZ02;01/01/2026;145600;01/01/2026;31/12/2026;
BRZCPACQ26;BRZ03;01/01/2026;178200;01/01/2026;31/12/2026;
BRZCPACQ26;BRZ04;01/01/2026;178200;01/01/2026;31/12/2026;
BRZCPACQ26;BRZ05;01/01/2026;178200;01/01/2026;31/12/2026;
BRZCPACQ26;BRZ06;01/01/2026;178200;01/01/2026;31/12/2026;
BRZCPACQ26;BRZ07;01/01/2026;52000;01/01/2026;31/12/2026;
BRZCPACQ26;BRZ08;01/01/2026;178200;01/01/2026;31/12/2026;