Before starting
Analytical sections are imported from a dedicated interface, which is accessible in the settings wheel at the top right of your environment.
To access this menu, you must have permission to import data.
If this is not the case, request this permission from your administrator or from the help desk.
Import of analytical sections
Path: Cogwheel (or settings) > Import > "Analytical sections" section
Here is an example of an analytical sections import file
The files expected by the import module are .csv with a semicolon separator or .txt
The file to be imported is composed of the following required data in the columns:
- code : it must be unique for sections on the same section
- name : the section label, in the language of the user performing the import. If you want to specify the language of the label, you need as many columns as there are translations, with titles in the name(xx-XX) format where xx-XX is the code for a culture. For example, fr-FR for French, en-GB for British English, en-US for American English, etc.
- axisid : the section ID. This is visible in the sections administration interface, top right.
And data that are not mandatory but have to be completed if you need a restriction on a defined population:
- isactive: allows you to archive a section with the value false or re-activate one with the value true.
- isPublic: accepts the value trueif the section is Public, and visible to all users.
By specifying false, you must indicate restrictions to users (identified by login, email or if you do not have people with the same name, the last name+first name pairing), departments or establishments in individual columns; always one after the other, with the comma as separator.
Updating analytical sections
You can update your analytical sections en masse by importing a file in the same format as the one used for importing, with the exception that the section column must not be column A, as in the example below to deactivate an analytical section with code 123 belonging to section 1:
Automating the flow of your analytical data
It is possible to schedule automatic imports.
The file for import must be stored on a FTP server, which will be queried each day. The file format to use is the same as for a manual import.
Parent/Child imports
Child-parent links between the sections:
- childrenAxisSections lists the child section(s) of a section. If your codes are whole numbers, the import module may confuse them with section login details, so use childrenAxisSections.code
- parentAxisSections work in the same way, although it is on the child lines
Importing of analytical values by default for users
The analytical sections can be attributed to your employees. These data will be visible and modifiable in their user file.
For a section to be linked to an employee, the "Appears on the user file" option must be activated in the required section.
The user value is indicated in the data file you import from the user data.
The name of the column to use in the import will be "axisValues.code". It must be filled in with the code of the analytical section to be matched to the user.
If there are several activated sections, you can specify a default value per section by putting several fields labeled "axisValues(1).code", "axisValues(2).code", etc. The ID of the section in question, displayed on the administration interface of the analytical sections, should be indicated in brackets.
Finally, the list of all the sections assigned to a user follows the cancel and replace rule: if there is at least one "axisValues" column in the file you are importing, all the users specified in the file will have their complete list reinitialized with the sections provided, even if only the values of one section have been imported.