In Lucca, you can set up an analytics plan to track expense analytics through Cleemy Expenses and activity analytics through Timmi Timesheet.
You can add to this analytics plan manually (Creating and managing analytical axes), or it can be updated automatically.
Automatically updating analytical axes
Automatic syncing occurs through an FTP server to which you uploaded a CSV file including the analytical axes you want to create or edit. This FTP server will be queried once a day by Lucca to carry out the import.
Two prerequisites are required to set up automatic syncing:
- The set-up of an FTP server. If you already have an FTP server, we can use it for syncing. Otherwise, we can create an FTP server managed by Lucca.
- The ability to adapt the file exiting your ERP or your accounting software to match the format supported by our import module.
The import file format
The file that will be uploaded to the FTP server for automatic syncing should be in CSV format and include different fields (their names must appear on row 1), 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 formatmultilingualName(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 thetrue value if the axis is visible to all users orfalse, 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 likedepartments,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 useusers.mail,users.login, etc. as the field name in order to tell the import module what data you are using.