It is possible to add tasks in bulk in the backoffice from CSV file.

Expected structure of the CSV file

Columns to configure the task

The task import requires the use of 6 columns to define it :

• Submission # structure_id: this column allows you to choose the form in which an import is to be carried out. The identifier (structure ID) can be found for example at the end of the form URL : ... / structures / builder / XXXX.
• Submission # userEmail: This e-mail identifies the user who created the file.
• type: here you have the choice between a simple task and a recurring task. In the current state, you can only import simple tasks. It is therefore necessary to put the value "simple".
• Start and End dates of the task: they must be entered in ISO 8601 format. Example: 2018-04-30T17: 00: 00 + 02: 00
  • start_date: this is the expected start date of the task.
  • due_date: this is the expected date of the end of the task.
• user_email: this column is used to assign the task to a Daxium user. You must enter the user's email address in this column.

Please note that you cannot assign a task to mobile users only.

Columns to configure the associated submission

Each task must be associated with a submission. To do this, you must first specify which form model you are working on. You must therefore include a Submission # structure_id column. This column must be filled in with the form identifiers compatible with the creation of tasks. This identifier can be found, for example, at the end of the form designer URL : ... / structures / builder / XXXX.

You can then fill in the submission fields. To do this, just do the same as in importing a submission, but prefixing the columns with Submission #. For example, to define the owner of the form (which is mandatory), you must create a Submission # userEmail column. To populate a list using external identifiers, this gives : Submission # ListSystemName # external.

In this way, you can fill in all the fields of a submission, even if they do not appear in the list of fields accessible when creating a task.

An example of a task import CSV is provided at the end of this article.

Setting up the import

Once your CSV file is ready, you need to upload it to Daxium-Air. To do this, go to the "Tasks" section, then click on "Import".

All you have to do is choose your CSV file and determine the separator you use (by default it is the comma in most countries, and semi-colon in France).

The import takes place in the background. You will be notified by the notification bell when it is finished.

Error management

When your import is finished, if ever an error prevented one or more submissions from being registered, you will have a return in a CSV file. This file is accessible from the notification bell.

The latter will allow you to understand what went wrong and how to correct the problem.