Automatically update analytical plans

Before you get started

In Lucca, you can set up an analytical plan to track expenses via Cleemy Expenses and activities via Timmi Timesheet.

This analytical plan can be manually populated (Create and manage analytical sections) or automatically updated.

Automatic updating of analytical sections

Automatic synchronization is performed via FTP, where you upload a CSV file containing the analytical sections you wish to create or modify. This FTP server will be queried once a day by Lucca to perform the import. 

There are two prerequisites for setting up automatic synchronization:

  • Setting up an FTP server. If you already have an FTP server, we can use it to synchronize your data. If not, we can set up an FTP server for you, managed by Lucca.
  • The ability to adapt the file coming out of your ERP or accounting software to the format required by our import module.

Import file format

The file to be uploaded to the FTP for automatic synchronization must be in CSV format and contain various fields (their names must be indicated on the first row), some of which are mandatory (marked with an *).

  • 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 label language, you will need as many columns as there are translations, titled with the following format multilingualName(xx-XX) where xx-XX is a culture code. For example, fr-FR for French, en-GB for British English, en-US for American English, etc.
  • axis*: the section login details. This is visible in the sections administration interface, top right.


  • active: allows you to archive a section with the false value or reactivate one with the true value.
  • 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 identifiers, so use childrenAxisSections.code
    • parentsAxisSections works in the same way, but on the child lines
  • isPublic: accepts the true value if the section is visible to all users, or false,in which case you must specify restrictions to users or departments.

Access restrictions are managed by 4 fields. Here you can indicate the individuals or departments authorized to assign to the section. Either in one column, separated by commas, or by creating as many columns as there are elements to authorize.

  • departments: specify the authorized services to be assigned to the section.
  • departmentsWithSubs: works like departments, except that sub-services of the mentioned services will also be included automatically.
  • users: allows you to specify which users have access to the section, preferably by providing their login. You can also use other unique user identifiers, such as email addresses. For added security, you can use the following field label users.mail, users.login, etc. to inform the import module what data you're using.

Page content

Was this article helpful?
0 out of 0 found this helpful