Skip to content

Dynamic database fields

Requires the "Dynamic database fields" permission.

Every contact has a set of standard fields, the same for everyone: company name, first and last name, address, up to nine phone numbers, email, website and two reference IDs (the full list is in Importing contacts). When a list contains extra information specific to your business (e.g. "Contract expiry", "Current supplier", "Power kW", "Customer since"), you manage it with dynamic fields.

Dynamic fields are grouped into schemas: a schema is a set of fields designed for a certain type of list (e.g. the "Energy" schema with "Current supplier", "Annual consumption" and "Contract expiry"). Each database can use only one schema, and all its contacts share the same dynamic fields.

You open the page from the menu DATA → Dynamic database fields.

The schema popup (here New schema; Edit schema is identical) contains the Schema name and three fields of different types, Text, Number and Date, each with its own Remove button.

What they are for

Once linked to a database, the fields of the schema appear throughout Thelgo:

Where How
Import The columns of the file can be loaded onto dynamic fields, like standard ones. Values are checked according to the field type
Correct database You can update (or empty) the dynamic fields of contacts already present with a correction file, for example to fill in a new field
Export database Every dynamic field becomes a column of the Excel or CSV file, and a column in the database preview
Operator's contact card While working on a contact, the operator sees the contact's filled-in dynamic fields, together with the contact details. With the "Edit contacts" permission they can correct them and fill in those still empty
Campaigns Dynamic fields can be used in contact filters (for Number and Date types also as a "from… to…" range) and in the ordering of the call queue
Contact search In a search on a database or on a campaign, dynamic fields appear among the choices of Other field
Surveys A survey can be tied to a schema: its questions can use the fields as placeholders ({{Field name}}) and the survey can be chosen only by the campaigns of databases with that schema. When you rename a field, the placeholders in the schema's surveys are updated; a field mentioned in a survey cannot be deleted (the window lists "N survey questions or options"); the schema of a database cannot be changed if one of its campaigns uses a survey tied to the current schema
Contact details The administrator sees and edits them
Calendar Dynamic fields appear among the data of the contact linked to the appointment

The list of schemas

Column What it shows
Name The name of the schema
Fields How many fields it contains
Status In use if at least one database uses the schema, otherwise Not used

Click a row to open and edit the schema. The trash can deletes it (see below).

Creating a schema

  1. Press + New schema.
  2. Write the Schema name.
  3. The first field is already ready to fill in; press Add field for every other field you need. For each field fill in:
    • Field name: the label that administrators and operators will see (e.g. "Contract expiry");
    • Type: one of those in the table below.
  4. Use Remove to take out a field added by mistake.
  5. Press Save. A new field left without a name (usually the first one, if you do not need it) is ignored: it is not saved as an empty field.

The fields appear in the order in which you entered them. Field names must be different from each other within the same schema (upper and lower case do not matter), otherwise a red warning appears at the bottom: "Field names must be unique within the schema."

You can also create a schema during the import: the + New schema button in step 1 takes you to this page with the creation popup already open.

Field types

Type Values accepted on import
Text Any value
Number Numbers with a comma or a point as decimal separator (e.g. "1250,50" or "1250.50")
Date Dates, preferably in day/month/year format (e.g. "31/12/2026")
Yes/No "Sì", "Si", "Vero", "Yes", "1", "X", "True" for yes; "No", "Falso", "0", "False" for no

On import, a value that does not match the type (e.g. "about 300" in a Number field) causes the whole row to be discarded as an error, with the message "Valore '…' non valido per il campo '…'" (Value '…' is not valid for the field '…'). The type also matters in campaign filters: only Number and Date fields allow filtering by range.

When in doubt, Text

If a column of your file contains mixed or "dirty" values, use the Text type: it never discards any row. Use Number and Date only if you need to filter campaigns by range and you know the data is clean.

Linking a schema to a database

A schema is linked to a database in two ways: you choose it in step 1 of the import, or from Edit database on the Databases page.

After the first contacts, the choice is final

As long as the database is empty (no contacts and no campaigns) you can change the schema, or remove it, from Edit database. As soon as the database has contacts or campaigns the schema is locked, and all imports use the same schema. Before importing the first list, make sure the schema contains all the fields you will need. You can still add fields to the schema later (see below).

Editing a schema

Click the schema in the list, make your changes and press Save. The popup shows the warning "Changing the fields of a schema already used by a database may require adjusting contacts already imported."

What happens to the contacts already imported:

Change Effect
Adding a field The new field is empty for all existing contacts. You can fill it in from the contact details or load it with a new import (only for new contacts: rows already present are discarded as duplicates)
Changing the type Not possible if at least one contact already has a value for that field: the red warning "Cannot change the type of field "…": at least one contact already has a value for this field." appears at the bottom
Renaming a field When you save the schema, Thelgo automatically updates everything that uses the old name: the contact values of the databases that use the schema, the filters and ordering of the campaigns already created, the filters of the contact blocks, the agents' filters and the {{field name}} placeholders in the email templates, in the SMS templates, in the appointment reminder templates (email and SMS) and in the campaigns' call script. Placeholders are updated even if they are written with spaces inside the braces, for example {{ Città }} (the spaces stay as you wrote them). The field name is matched exactly, uppercase and lowercase included. Everything happens in a single operation: if something goes wrong, no change is applied.
Deleting a field (Remove) The values of that field are permanently deleted from all the contacts of the databases that use the schema (see Deleting a field)

Deleting a field

If you remove with Remove a field already present in the schema and press Save, Thelgo checks what this involves and, if needed, opens the Removing dynamic fields window. For each field you are deleting it shows the name and:

  • "N contacts have a value in this field", if any contact has a value;
  • "It cannot be removed while it is used in:" followed by the list of uses, if the field is still referenced by name.

The uses that Thelgo checks are:

List item Where the field is
"N campaign selection filters" Campaign contact filters
"N agent filters" Agent filters
"N block filters" Filters of the contact blocks
"N campaigns as sort order" Ordering of a campaign's call queue
"N campaigns in the script or welcome message" Placeholders in a campaign's call script or VoiceAI welcome message (even with spaces inside the braces)
"N email/SMS templates" {{field name}} placeholders (even with spaces inside the braces) in the email templates, in the SMS templates and in the reminder templates

For a field with values in the contacts, the Removing dynamic fields window shows a red warning and the box "Type delete to confirm:". Delete values and save stays off until you write the word.

What happens:

  1. Field still in use. In the window you read "Remove these uses first, then try again." and you can only press Close: the field is not deleted as long as it is referenced by filters, orderings, scripts, welcome message or templates. If you try to save anyway, the warning is "Cannot delete field "…": it is still used in …. Remove these uses first." Remove the uses (in the campaigns, in the blocks, in the templates…) and try again.
  2. Field with values, not in use. The window warns "The values of these fields will be permanently deleted from the contacts. This cannot be undone." and asks "Type delete to confirm:". Write delete (upper and lower case do not matter; the word is in the interface language) and press Delete values and save. With Cancel you go back to the popup without changing anything.
  3. Field without values and not in use. It is deleted without asking for confirmation.

If something changes between opening the window and saving (for example another administrator imports new values), the save may be rejected with "Field "…" has a value in … contacts: confirm the deletion of the values to continue.": press Save again and confirm.

Deleted values cannot be recovered

The values are deleted together with the field. If in the future you create a field with the same name, it starts empty: it does not get the previous values back. If you still need the data, export the database before deleting the field.

Renaming a field is safe

Contacts, campaigns (filters, ordering, blocks, scripts), agent filters and email and SMS templates follow the new name without you having to do anything else.

Only fields with at least one value

In campaign filters and in Other field of the search, only the fields (standard or dynamic) that have at least one value in the database's contacts appear. A dynamic field that has just been added and is still empty does not appear until you fill it in on some contact.

Deleting a schema

Press the trash can on the row and confirm the question "Delete the schema "…"?". You can only delete schemas that are Not used: for those In use the trash can is disabled. A schema stays in use as long as at least one database is linked to it; if you delete that database from the Databases page, or if you unlink it from an empty database with No schema in Edit database, the schema can be deleted again.