You can import analytical axes from the settings cogwheel at the top right. To access this menu, you need permission to import data. If you do not have access, ask your administrator or the help desk for permission.
Importing analytical axes
From the settings cogwheel > Import > Analytical section, you can import CSV files to create numerous sections, with one line for each section to be created or modified.
The file has different fields (put their names on the first line), some of which are mandatory (marked with an * below).
- code*: it must be unique for sections from the same axis.
- name*: the title of a section, in the language of the user doing the import. If you want to specify the title’s language, you will need as many columns as translations, named using the format multilingualName(xx-XX), where xx-XX is the code for a culture. For example, fr-FR for French, en-GB for British English, en-US for American, etc.
- axis*: the axis’ identifier. This is visible at the top right of the axis management interface.
- active: allows you to archive a section using the false value or reactivate one using the true value.
- The parent-child relationships between sections:
- childrenAxisSections makes it possible to list a section’s child section(s). If your codes are whole numbers, there is the risk that the import module will confuse them with the axis identifiers, so instead use childrenAxisSections.code
- parentsAxisSections works the same way, but on child lines
- isPublic: takes the true value if the axis is visible to all users or false, in which case, you must indicate restrictions on users or departments.
Access restrictions are managed via 4 fields. Here, you can indicate which people or departments are permitted to post on the section. Either in one column using a comma separator or by creating as many columns as items to authorise.
- departments: provide the name of the departments permitted to post on the section.
- departmentsWithSubs: works like departments, except that sub-departments of the departments indicated will also be included automatically.
- users: allows you to indicate which users can access the section, preferably by providing their login. You can also use other unique identifiers for the users, such as email addresses. For better reliability, you can use users.mail, users.login, etc. as the field name in order to tell the import module what data you are using.
You can also schedule automatic imports. The file being imported must be on an FTP server, which will be checked daily. Use the same file format as you would for a manual import.
Importing default analytical values for users
You can assign analytical axes to your employees. You can view and change this piece of data in their user file.
To link an axis to an employee, you must enable the ‘Display in user page’ option in the desired axis.
You can then run a user import to fill in this field.
Use the column named ‘axisValues.code’ in the import. You must complete it using the code for the analytical section you want to associate with the user. If multiple axes are enabled, you can specify a default value per axis by including several fields called ‘axisValues(1).code’, ‘axisValues(2).code’, etc. You should provide the identifier (visible on the analytical axis management interface) for the axis in question in parentheses.
Lastly, the list of all axes assigned to a user adheres to the cancels and replaces rule: if there is at least one ‘axisValues’ column in the file you are importing, all users indicated in the file will have their entire list reset with the axes provided, even if values for only one axis were imported.