Skip to content

Correct database

Requires the "Databases" permission.

Correct database is used to fix a wrong import in bulk. Instead of deleting the database and importing again, you upload a correction file: Thelgo looks up every contact already present and updates its data, without creating new ones. This way you do not lose the campaigns, outcomes and call history linked to those contacts.

Typical examples: a column imported into the wrong field, ZIP codes without the leading zero, a dynamic field that did not exist yet or was empty, phone numbers to fix.

The function is opened from the Databases page, with the Correct database icon (wrench) on the row of the database to correct. The wizard has two steps: 1. File → 2. Confirm.

Before you start: prepare the file

The correction file follows the same rules as the import file: Excel .xlsx or .xls, or CSV, at most 26 MB, with a header row recommended. In addition:

  • every row must contain a phone number that Thelgo uses to recognize the contact to correct (the control field, see below);
  • include in the file only the columns you want to update (plus the control phone column).

Export first, then correct

To start from safe data you can export the database, fix the file in Excel and upload it again here. The exported file contains the Id column, which is not needed here though: Thelgo recognizes contacts by phone.

Step 1: File

At the first step, Correct database shows the line "Database to correct", the Available fields box and the choice of the Excel or CSV file.

At the top you read Database to correct with the name of the chosen database. The Available fields box lists the fields you can update: the standard ones and the dynamic ones of the database's schema (if it has one). In an RPO database the only phone available is Phone 1.

  1. Choose the file in Excel or CSV file and press Next. If the Excel file has several sheets, "The file contains several sheets: choose which one to use" appears: click the name of the sheet.
  2. In Field matching, match each column of the file to a Thelgo field. Thelgo proposes on its own the matches it recognizes. Columns left on Don't import are not used. Each field can be used only once, and at least one column on a Phone field is required ("Select at least one column to map to a Phone field.").
  3. Choose the Control field.
  4. Set the Options and press Next.

The control field

The control field tells Thelgo which contact to correct for each row: you choose it among the columns matched to a Phone field (e.g. "Phone → Phone 1"). Thelgo looks in the database for the contact that has that number in that very phone field (if you choose Phone 1 it searches only among the Phone 1 values, not among the others). The number is cleaned as in the import: only the digits are kept and a leading "+" becomes "00".

The control field is only used to find the contact and is never modified. To correct the number itself, put two columns in the file: the one with the old number matched to the control field, and the one with the right number matched to another Phone field.

Options

Option What it does
Skip first row (header row) (on by default) Does not use the first row of the file. Leave it on if the first row contains headers; turn it off only if the file contains data only, otherwise the first row would be skipped
Check leading zero (on by default) Restores the leading zero lost by Excel on phone numbers and ZIP codes, as in the import

Step 2: Confirm

Check the Field matching summary (Source field → Destination field, with the Control field label next to the chosen field) and press Start correction.

The correction starts in the background: you see a progress bar with the number of rows processed. You can leave the page open or go elsewhere, because the correction continues even on large files, and you find its result on the Operations page (type Database correction).

The correction changes the data immediately

There is no preview and it cannot be undone: try first with a file of a few rows, or make an export of the database to keep as a copy.

What gets updated

For each row found, Thelgo writes the values of the matched columns:

  • a filled cell replaces the current value of the field;
  • an empty cell empties the contact's field (also a dynamic field): if you do not want to touch a field, do not match its column;
  • dynamic fields are checked according to their type (Number, Date…), with the rules of the import;
  • phone numbers are cleaned as on import and must not already belong to another contact of the same database.

A discarded row (phone conflict, invalid or too long value) does not change any data of the contact, not even partially: either the row is applied in full, or it is not applied at all.

Fields you do not match stay unchanged. The contact's outcomes, campaigns and appointments are not touched.

The result

At the end Correction completed (or Correction failed) appears with four figures:

Figure Meaning
Total Rows of the file processed
Updated Contacts found and updated
Skipped / not found Rows not applied: empty control field, contact not found or phone conflict (see below)
Errors Invalid rows

From here you can go back to the Databases page with Back to databases or open View the operation log.

In Operations the Imported column counts the contacts updated and Discarded the rows skipped, not found or in conflict. The row-by-row log has these outcomes:

Outcome in the log When
Updated The contact was found and corrected
Skipped (empty check field) The cell of the control field is empty ("Valore del campo di controllo vuoto." (Control field value is empty.))
Not found No contact in the database has that number in the control field ("Nessun nominativo trovato con '…' = '…' in questo database." (No contact found with '…' = '…' in this database.))
Discarded (phone conflict) A new number in the file already belongs to another contact in the database ("Numero già presente su un altro nominativo del database: …" (Number already present on another contact in the database: …))
Error Value not valid for the type of a dynamic field, or too long for the field (e.g. "Valore troppo lungo per il campo 'Provincia' (massimo 2 caratteri): '…'" (Value too long for the field 'Provincia' (maximum 2 characters): '…')), or a number 9999999999 ("Numero di telefono riservato non valido." (Invalid reserved phone number.)): it is the number reserved for anonymized contacts and cannot be used even as a control field

The final status is Completed if there are no errors, Completed with errors if at least one row is in error, Failed if the correction stopped because of an unexpected problem (rows already corrected stay corrected). In the log, the Errors and Discarded filters refer only to the rows of type Error and Discarded (duplicate) of the import: to see the rows not found or in conflict use All.

Every correction is recorded in the Audit log with the action Contacts corrected, with the summary of updated, skipped, not found, conflicts and errors.

Correct database does not create contacts

Rows of the file that do not match any contact are ignored (outcome Not found). To add new contacts use the import.