Skip to main content
Custom Data

Learn more about custom data types and how to use them in your operations.

e
Written by eLogii
Updated over a week ago

Custom data allows adding additional data fields for use throughout various entities within eLogii.

There are two ways of adding custom data.

Configuration settings

To set up Custom data go to Configuration β‡’ Custom data

You will be able to set up custom data for Tasks, Items, Drivers, Vehicles and Routes by switching through different options on the top bar. You can specify a custom field for any of the entities separately. The options are the same across all entities and the same Custom data logic applies to all entities.

Click Save once all the data has been added.

There are different Field types to choose from :

  • Text/ Number - This allows you to add a field to add any text or number values.

  • Dropdown - Creates a list of options you can choose from

  • True/False (Yes/No) - Creates a Yes/No dropdown

  • Multiselect dropdown - Lets you select multiple items

  • Date - Allows users to add a Date picker to the desired entity

Value types can also be specified - they can be either Text or Number, and this determines the acceptable input values.

Available values - Lets you specify values for the dropdown selection types

This extends to the filters – the custom data section shows the predefined filters options You can still add any custom data that is not available

πŸ’‘ Pro Tip

In Text Custom Fields you can embed links to external sources (for example, a way to redirect Drivers redirect them to our external support site) and have them displayed to your Drivers in the Driver App.

Go to Configuration > Driver app > Enable Task Custom data. Now Task Custom data will be shown for the Drivers, which can include not only links, but any bits of information you want them to see.

Custom Data through entity options

This is another method of adding custom data and it can be done through any of the following entities’ option settings.

For example, if a driver has a specific personal code you use in your internal system to identify them, custom data can be added for him in the following way:

Key: PERSONAL CODE

Value: 123456

You can search by this custom data item in the Advanced Filters section.

Please keep in mind that every Custom field added on an entity level will apply to only the entity it has been added to, and not to all entities of the same type. For example, if you add a Custom field for Driver 1, it will only be available to be populated for Driver 1, and not for all other Drivers.

At the moment, adding Custom data on an individual entity level is currently limited in terms of field options, as it's only possible to add a Key and Value and is not refined as Custom Field creation through Configuration.

Driver custom data

Adding custom data for a driver can be done in Drivers β‡’ Driver Profile β‡’ Custom Data.

Click Update once the data has been added.

Task Custom Data

Adding custom data for a task can be done in Tasks β‡’ Task Profile β‡’ Custom Data.

Click Update once the data has been added.

Vehicle Custom Data

Adding custom data for a vehicle can be done in Vehicles β‡’ Vehicle Profile β‡’ Custom Data.

Click Update once the information has been added.

Vehicle Type Custom Data

Adding custom data for a vehicle type can be done in Vehicles β‡’ Vehicle Types β‡’ Vehicle Type Profile β‡’ Custom Data.

Click Update once the information has been added.

Items Custom Data

Adding custom data for an item can be done in Tasks β‡’ Task Profile β‡’ Items β‡’ Add task item β‡’ Custom Data.

Click Save once the data has been added

Importing custom data via CSV

To import custom data via CSV, the column name needs to follow a set convention, and it should be customData.Field Name. For example, customData.Comment. You can only import Custom data that's previously been created in eLogii, so make sure to do that before proceeding. This custom data input rule applies for Vehicle and Driver custom data as well.

For items, the custom data column naming convention goes items[number of the item].customData.Field Name (for example items[0].customData.Item Comment). For more information on importing Items, please refer to this article. You can read this article if you would like more information on general CSV import.

You might also be interested in:

Did this answer your question?