Academy
Task Management

Bulk task registration

Bulk task registration is an advanced feature of Task Management. With it, you upload a single spreadsheet with a batch of tasks — title, description, deadlines, and assignees — and the platform creates all of them at once. It is the recommended path when you need to register many tasks at the same time, instead of creating them one by one.

Before you start

This is an implementation flow: it depends on a technical configuration made by the Dattos team before the first use. For new customers coming from the sales process, the environment is delivered already prepared. If the feature is not yet available in your environment, contact Dattos Support.

The prerequisites for the feature are:

  • Access to the screens Copy and Restore Settings, Folders, Tasks, and File Upload.

  • Environment on version 13.6.4 or higher of Dattos.

  • Bulk registration configuration package deployed (described below).

How it works

Bulk registration has three components:

  1. Configuration package: enables the feature and is associated with the folder where the tasks will be created. Deployed by the Dattos team.

  2. Template spreadsheet: where you describe the batch of tasks, one per row.

  3. Upload: sending the spreadsheet through the platform, which then generates the tasks.

Configuration package

Bulk registration depends on the TASKS-CONFIG (Dattos Tasks Settings) package, which enables advanced Task Management features. It is not customizable. Deployment is done by the Dattos team and involves:

  1. Restoring the configuration package in the client base.

  2. Associating the package with the root folder of the folder structure where tasks will be registered. E.g.: the Monthly Closing Tasks folder.

  3. Linking the package to the privacy profiles with allowed access.

Important: associate the package only to the root folder of the structure where the tasks will be created. The package version depends on the platform version: use TASKS-CONFIG_v1.1 on version 15.0 or lower, and TASKS-CONFIG-v2.0 on version 15.1 or higher. Applying the wrong version causes configuration failure.

Filling out the template spreadsheet

Download the template spreadsheet corresponding to your platform version and fill in one task per row. The columns are:

  • Folder Code (mandatory): the code of the folder where the task will be created. E.g.: F1.

  • Task Title (mandatory): the name of the task. E.g.: Prepare financial report.

  • Start Date (mandatory): the start date, in DD/MM/YYYY format. E.g.: 01/01/2024.

  • Due Date (optional): the deadline. E.g.: 31/01/2024.

  • Delivery Time (optional): the due time, in 24-hour format HH:MM. E.g.: 08:30, 23:00. Do not use commas, text, or abbreviations like "AM" and "PM".

  • Description (optional): the details of the task.

  • Creator (Login or Email) (mandatory): who creates the task. The reported creator is linked to the Reporter field. E.g.: username or [email protected].

  • Assignees (Logins or Emails) (optional): one or more assignees, separated by commas. E.g.: username1, username2.

Important: use the template spreadsheet corresponding to the package version. In version 15.0 or lower, use the spreadsheet Dattos Tasks Registration v1.1. In version 15.1 or higher, use Dattos Tasks Registration v2.0.

Uploading the spreadsheet

With the spreadsheet filled and saved:

  1. Go to Import → File upload.

  2. Upload the task spreadsheet.

  3. Confirm the destination folder and process the file.

The platform creates the tasks automatically. Then, open the Tasks screen and check if the batch was registered correctly.

Important rules

  • Folder structure: registration only occurs for folders in the same structure where the import is made (the root folder and its children).

  • No duplicates: duplicate tasks are not registered. Uniqueness is checked by the combination of Folder Code + Task Title + Creator + Start Date.

  • Recurrence is not imported: bulk registration creates the basic structure of the task. Recurrence needs to be added later, directly in the platform, to each task.

Was this helpful?