Object of the interface
The interface allows you to import rate grids into Timesquare. The principle is to provide the expected information in a text file that will be read and interpreted by the interface in order to update the database.
Learn more about setting up this import.
File name
Unique file
The name of the file is up to the user (label + extension) but once defined in the setting of the import, it must not change anymore.
Examples: RateGrid_A.txt, RateGrid_Timesquare.001, RateGrid.csv.
Multiple files
The file name must comply with a specific syntax including the date of the data provided. The Label field must define the naming chosen. Thus, LabelJJMMAAAA.EXT, LabelJJMMAA.EXT, LabelAAAAMMJJ.EXT or LabelAAMMJJ.EXT are the supported wordings in which:
- "Label" is made of a string of alphanumerical characters that can be personalized
- "JJ" stands for the day (DD), "MM" stands for the month, "AA" and "AAAA" stands for the year (YY or YYYY), that can be indifferently written with 2 or 4 characters
- "EXT" is an alphanumerical string with 3 characters maximum that can be personalized
Example 1: the Label field in the configuration is named RateGrid_JJMMAA.txt and the three import files are named RateGrid_040520.txt, RateGrid_050520.txt and RateGrid_060520.txt.
Example 2: the Label field in the configuration is named RateGridAAAAMMJJ.001 and the three import
files are named RateGrid20200504.001, RateGrid20200505.001 and RateGrid20200506.001.
Example 3: the Label field in the configuration is named AAMMJJ.txt and the three import files are
named 040520.txt, 050520.txt et 060520.txt.
Format
Text. UTF-8 encoding.
Separator between two information
The separator between two pieces of information is the semicolon.
Description of the file content
Header
| # | Field name |
Type | Max size |
Note |
|---|---|---|---|---|
| 01 | Structure concerned | Alphanumerical | 38 | Structure code |
| 02 | Label | Alphanumerical | 255 | Label of the grid created |
| 03 | Application start date | Date | 10 | According to the format selected in the configuration |
| 04 | Application end date | Date | 10 | According to the format selected in the configuration |
| 05 | Description | Alphanumerical | 255 | Optional field, associated description |
Following rows
| # | Désignation | Type | Taille max |
Remarque |
|---|---|---|---|---|
| 01 | Group | Alphanumerical | 38 | Group code |
| 02 | Qualification | Alphanumerical | 38 | Qualification |
| 03 | Level | Alphanumerical | 38 | Level code or empty |
| 04 | Hour rate | Numerical | Positive real value or null | |
| 05 | Coefficient (workload) | Numerical | Positive real value or null | |
| 06 | Delta hourly rate | Numerical | Positive real value or null |
Rules
- A grid is created based on the information in the first row. For each valid line of the file, we insert a row containing the cost information. A row is considered valid if all required columns are filled in correctly. At a minimum, a cost row must be populated for the row to be imported and the grid created.
- The Structure column contains the code of the structure on which the form will be created.
- The Title column feeds the Title field of the form. It cannot be empty.
- The Period start date and Period end date columns populate the Application period field
of the rate grid. - The period end date must be greater than or equal to the period start date.
- The Description column feeds the Description field of the grid. It can be empty.
- All columns, even empty ones, must be present in the file.
- The Level column can be empty.
- A group / qualification / level association is unique and can only appear once
in the list.
If several rows contain the same group / qualification / level associations, only the
first encountered is inserted, the others are discarded.
Example of content
TEST;CREATIONFICHE;15/03/2023;31/12/2023;DESCRIPTION;
ACTIFS;RZ;E1;10;1;0.5;
Comments
0 comments
Please sign in to leave a comment.