Title page

File:Liquid Data Manager 01.png

Liquid Uploader V3.0

User Guide




Dialler A mechanism which prioritises, and schedules leads to contact.
Lead A customer record with a minimum of one contact, and a name. A URN is generated for each lead
Telephony Provider A system which makes telephone calls
URN Unique Reference Number
Contact A telephone number, or an address.
Contact Method A system for contacting the lead. For example a preview dialler, or a 3rd party predictive dialler.


The Liquid Uploader tool serves two purposes. It enables users to insert leads into the Liquid system for dialling and it allows users to move batches between contact methods.

The process involves the following steps.

File:Liquid Data Manager 02.png

Figure 1 Top Level Upload Steps

These steps are explained in detail in this manual.

For moving batches between contact methods (see Batch Management)

For all activities you must be logged into the Uploader (see Logging into Liquid), have sufficient rights assigned to you to upload data, and be connected to the internet.

Logging into Liquid

File:Liquid Data Manager 03.png

Figure 2 Liquid Application (not logged in)

Click the Logon Button on the Toolbar.

File:Liquid Data Manager 04.png

Figure 3 Login Dialog

Provide your username, password and Liquid Centre ID.

Liquid will remember your username and Centre ID

Click Logon to login to liquid.

Changing Your Password

You can change your password from the Login Dialog. Click Change password.

File:Liquid Data Manager 05.png

Figure 4 Change Password

Clicking Change will change the password and logon to liquid.

Logged in.

After you are logged in the application will automatically start polling the server to update the upload progress screen. You will see a list of files which have been uploaded recently (see Upload progress).

The title bar of the Uploader displayed the logged in user, the call centre and the address of the server to which you are connected.

File:Liquid Data Manager 06.png

Figure 5 Liquid Application (logged in)

Open Data File

The Uploader supports the following file formats:

  • Delimited text file (for example comma, tab separated.)
  • Microsoft Excel Document.

In both cases the first row of the data must contain the column headings.

Drag the desired file onto the Liquid upload tool, or from the main menu select File -> Open Customer Upload File.

The Uploader will automatically ask you to login if required.

The Uploader will remember the last directory you uploaded data from.

You will be presented with options relating to the chosen format. In the case of an Excel file, you must choose the sheet from which the data should be taken. In the case of a character delimited file, the user will be presented with a simple import wizard:

Import Wizard Screen 1 – Excel File Options

File:Liquid Data Manager 07.png

Figure 6 Excel Import Options

Choose the sheet containing the data.

For best results ensure all columns in the Excel Sheet are stored as text. For example if a telephone number is stored as numeric data the preceding 0 will be stripped during the import. And if a date is stored as a date rather than text it will be subject to the local machine’s conversion rules during the import (ie dd/mm/yy instead of mm/dd/yy depending on the Window’s user’s locale.)

Import wizard screen 1 - Text File Options

File:Liquid Data Manager 08.png

Figure 7 Text File Import Options 1

File:Liquid Data Manager 09.png

Figure 8 Text File Import Options 2

The uploader will attempt to guess the format of your data and set the options accordingly.

Campaign Details Page

File:Liquid Data Manager 10.png

Specify the Campaign, Contact method and Batch from the drop down menus.

You can add a new batch by clicking new batch.

File:Liquid Data Manager 11.png

Figure 9 Adding a new Batch

Lead Expiry Page

File:Liquid Data Manager 12.png

Figure 10 Lead Expiry Page

Select the expiry date for the leads.

De-duplication Options Page

By selecting a de-duplication scope other than None, the Liquid Servers will reject duplicated leads. You can download the row numbers which were rejected and a reason, you can then correct these leads and choose to upload them again (see Upload progress). The leads which are not duplicated will have been inserted into the Liquid system.

In a future version of the Uploader you will be able to download all the schema fields in addition to the row number and error reason for each rejected lead. This will make it easier to make a repaired upload file to load.
File:Liquid Data Manager 13.png

Figure 11 De-duplication Options Page


None – no de-duplication will occur.

File – the server will reject duplicated records in the file.

Batch – the server will reject duplicated records in the file and the selected batches

Campaign – the server will reject duplicated records in the file and all batches in the campaign.

Batches to de-duplicate against.

Tick the batches you want the server to de-duplicated against when the scope is batch

The Uploader will automatically check the target batch for the file. You can uncheck this if you want to.
File:Liquid Data Manager 14.png

Figure 12 De-duplication Options Page (showing batches)

Schema Fields to De-duplicate against.

Select the fields to de-duplicate against; the available fields will depend on the schema defined for the Campaign. These fields are concatenated during the de-duplication operation.

For example: if telephone and Customer_Name are picked then Liquid will concatenate the phone number and the Customer_Name during the de-duplication operation. This will allow duplicates in the telephone field so long as the corresponding Customer_Name field is different.

The Uploader will remember the settings from the last file uploaded to the same campaign.

Finishing the Import Wizard

Click finish to complete the import wizard

For large files (typically > 30,000 rows) there can be a noticeable delay whilst the data file is imported into the Uploader.


Blank Lines
File:Liquid Data Manager 15.png

Figure 13 Blank Lines In Upload File

The uploader will reject data with blank lines. If you encounter this message then edit the original file to remove the blank lines.

If several rows are deleted from the end of an Excel sheet sometimes the Excel sheet stores those lines as existing but blank, rather than no lines at all. If the uploader complains of blank lines at the end of an Excel sheet, then open the document and delete the offending lines from the end of the sheet. You can check for blank lines in Excel by pressing Ctrl + Arrow Down. This should stop at the end of the data and then on the next click go to the end of the sheet.

Map Columns to Campaign Schema

Having imported a file, the next step is to match the fields within the file to those within the campaign.

File:Liquid Data Manager 16.png

Figure 14 Column Mappings Screen

On the left hand side of this screen, the data from the imported file can be seen. Those columns coloured green have been matched to the fields within the campaign. Any remaining columns have not been matched.

The columns are mapped by using the drop down boxes on the right hand side of the screen. These fields are colour coded:

  • Green fields denote fields which have been mapped.
  • Blue fields are yet to be mapped.
  • Red fields have yet to be mapped and are mandatory.

Once all of the mandatory fields have been mapped, the ’upload file’ button (bottom right hand side) will become active. Clicking on this will start the upload process.

Mapping Schema Fields

The list on the right hand side of the application contains all of the schema fields which can be mapped.

You can satisfy a mapping by selecting one of the following options from the drop down box.

File:Liquid Data Manager 17.png

Figure 15 Mapping Fields


In this case the schema field will contain no data. Note you cannot specify ignore for fields marked as compulsory.


The data for this field will be derived from the data in another column. See Derived Data for more information.

File Column Name

The data is taken from the column with the heading name you have picked in the list.


Each field in the schema for the Campaign can have an optional validation string associated with it. The validation string is a regular expression which the data must match before the uploader will allow the data to be uploaded.

The validation for each field is specific to the Campaign brief and is contained in the schema for the campaign, for example you might specify that a date format be dd/mm/yy.

See Correcting Invalid Data for more details about validation.

Derived Data

Any schema field can be satisfied by deriving the data from a specified column in the data file via a transformation.

Derived Data is a specialised, but powerful feature of the uploader. Consider contacting support for how you might use this advanced option.

When you select <derived> from the drop down in the column mapping you get some new options in the top right hand side of the application to configure the derived data.

Generic Derived Data

In the generic case for deriving data you will see the following options:

File:Liquid Data Manager 18.png

Figure 16 Generic Derived Data options

The transformation options consists of an extraction string, an output format string, and a derived from column.

The extraction string is a regular expression for extracting string(s) from the specified "Derived From" column.

Regular Expressions are powerful but can be difficult to write. There are various resources available (for example Please contact support for help when writing regular expressions.

The uploader substitutes occurrences of {n}, where n is a number, in the output format with the corresponding (nth) extracted string.

The uploader appends a column on the end of the data to store the derived column.

For example, say you always got your date data in the form dd/mm/yy but you need to upload the data in the form mm-dd-yy.

You could use the following extraction string to extract the dd, mm and yy parts from the date column:

^([0-9][0-9])[/]([0-9][0-9])[ /]([0-9][0-9][0-9][0-9])$

This would extract three strings from in the form of 3 groups of 2 digits separated by / characters.

You could then specify an output format like follows:


The uploader will substitute the first match with the {1} the second with {2} and so on.

File:Liquid Data Manager 19.png

Figure 17 Example Derived Date Column

You can see the result. In the pink column, the forward slash character has been replaced with a hyphen and the month and day extracted strings have been swapped.

Note the column is pink because derived columns still have to pass the validation for the field, in this case the Date_of_Birth field enforces a dd/mm/yy format which the derived column fails.

Changing the output format to


Causes errors to disappear and the column to go green.

File:Liquid Data Manager 20.png

Figure 18 Example Derived Column Valid Data

Timezone Derived Data

The Liquid system supports marking a lead with a timezone. This timezone information affects call backs, and allowed times for dialling. The timezone must be specified in the olson zoneinfo format (see )

If you select the derived option for a timezone schema field, a more specialised derived data options page is available.

These options allow you to specify a column containing an ISO code to derive the tz location from.

File:Liquid Data Manager 21.png

Figure 19 Derived Timezone Column

Correcting Invalid Data

All validation errors are listed in the error list at the bottom of the application. Double clicking on the error in the list will automatically highlight the cell with the invalid data. The screenshot below shows a date which has two forward slashes instead of one:

File:Liquid Data Manager 22.png

Figure 20 Example Validation Error

File:Liquid Data Manager 23.png

Figure 21 Validation Error Magnified

Clicking in a cell in the data grid places the grid into edit mode, and you can change the data.

File:Liquid Data Manager 24.png

Figure 22 Grid In Edit Mode

One the data has been changed the Uploader will re-validate the data.

The error goes away and the grid turns green.

File:Liquid Data Manager 25.png

Figure 23 Corrected Validation Error

Whenever possible it is best to specify the expected data types in the Campaign brief so that a suitable validation expression can be enforced. This will save many problems with the data down the line. Many different validation formats can be used, please contact support for advice.

Uploading Data

Once all the fields are mapped and any validation errors dealt with the data can be uploaded. Clicking on the upload button brings up the upload screen.

File:Liquid Data Manager 26.png

Figure 24 Upload Screen

The upload screen shows the progress of the file upload. First of all the data is processed, compressed and then local copies of the files to be uploaded are stored in the users temporary folder.

Once the local files are created the file is marked as resumable – this means that you can restart the upload if a failure occurs.

The Uploader then transfers the file in chunks to the server. You can see the progress on the dialog until it completes.

At any point the upload can be cancelled.

Once the data has been uploaded to the Aeriandi servers various server side processes are scheduled. You can monitor the server side processes, in the Upload Progress screen (see Upload progress.)

Resuming Uploads

If an upload is cancelled you can resume the upload by right clicking in the Upload Progress screen on the upload (it will be orange.)

When the Uploader Application is started it will detect any resumable uploads and prompt you.

File:Liquid Data Manager 27.png

Figure 25 Partial Upload Found

Upload progress

The upload progress screen is automatically displayed when you start the Liquid Uploader Tool. If you close the window you can reopen it from the View menu.

The annotated screen shot (see Figure 26 Upload Progress Screen) shows the upload progress screen and explains all of the columns.

File:Liquid Data Manager 28.png

Figure 26 Upload Progress Screen

ID This is the unique identifier for the file. Status The overall status of the upload
TimeStamp This is the time the upload was started Batch The target batch for the file
File Name The original filename of the data file Records The number of records in the file
Campaign The destination Campaign for the data file Rejected The number of rejected records in the file
Operation The current operation which is in progress ExpiryDate The expiry date for the records in that file
Progress The progress of the current operation    

1.1 Upload Progress Context Menu

Right clicking on a row in the Upload Progress grid provides the following options:

File:Liquid Data Manager 29.png

Figure 27 Upload Progress Context Menu

View More Detail

This provides more detail about the file, including who uploaded the file and it details every step undertook at the server.

File:Liquid Data Manager 30.png

Figure 28 Upload File Details

View Upload File Metadata

File:Liquid Data Manager 31.png

Figure 29 Upload file metadata

Using this dialog box you can add notes to the file. The fields which can be edited for each file are specified in the Campaign.

Download Generic Dial File

This allows a generic dial file (which can be uploaded into 3rd party diallers) to be downloaded.

For specific dial files a report must be run and downloaded from the reporting site.

A future version of the Uploader will provide access specially formatted dial files for specific 3rd Party diallers.

Reset Upload

This is for resetting the Upload in the case there is a server side failure. This is an advanced feature to be used with advice from Support only.

Resume Upload

Clicking on resume upload will resume a partial upload.

Download Rejected Record List

If the number of rejected records > 0 then you can download a list of the rejected URNs. This list includes the affected URN and the reason for the rejection. Usually this will be because of a de-duplication failure on the server. However any step, such as TPS, or an incorrectly formatted phone number could cause a record to be rejected.

In a future version of the Uploader the field information for that record will also be included which will make it much easier to upload the data once repaired.

Batch Management

It is possible to move batches between contact methods using the batch management functions within the Liquid Uploader.

If using a 3rd party dialler then you must ensure the data is synchronised between the Liquid and dialler system. Especially if moving from preview dialling to predictive. Please contact support regarding this operation.
File:Liquid Data Manager 32.png

Figure 30 Batch Management

Select the row you want to change. Use the combo box on the right hand side to change the contact method. You will be asked to confirm the change.



Microsoft Windows .net 2.0.

Installation Procedure

You can find the latest version of the Uploader here:

Uploader V3/

Download and unzip the installation media for example:

Aeriandi Liquid Uploader V3 Setup

Run Setup.exe to install the application.

File:Liquid Data Manager 33.png

Figure 31 Installation Security Warning

Click Run

File:Liquid Data Manager 34.png

Figure 32 Installation Wizard Page 1

Click Next.

File:Liquid Data Manager 35.png

Figure 33 Installation Wizard Page 2

Specify the location for the Uploader to be installed.

File:Liquid Data Manager 36.png

Figure 34 Installation Wizard Page 3

Click Next, the application will install when complete you will see the following page.

File:Liquid Data Manager 37.png

Figure 35 Installation Wizard Last Page (Installation Complete)

After installation a short cut will be placed under the start bar -> All Programs -> Aeriandi -> Aeriandi Uploader V3

Configure the Aeriandi Site Address Setting

The installation will install the default settings for the Uploader.

You should ensure that the AeriandiSiteAddress is set correctly for your organisation – this setting can be found in the Advanced Tab of the Options Dialog (see section "12.2.3 AeriandiSiteAddress").

To get the correct setting please contact the support department.


The Options Dial is available from the main menu, Tools -> Options. After making any changes to the settings you must restart the application.

File:Liquid Data Manager 38.png

Figure 36 Options Dialog

Upload Progress List Tab

This tab contains one setting:

Number of Months Back

This adjusts the range of files visible in the Upload Progress screen within the Uploader. If you selected 6 months then you would see all the uploads for the last 6 months.

Advanced Tab

File:Liquid Data Manager 39.png

Figure 37 Options Dialog - Advanced Tab


If set to true (default) then the application accepts https sessions to a server which has self signed certificates. If it is set to false then the application will only establish a connection to an https server with a certificate signed by a certification authority which has been granted root level trust in Windows.


The time in ms the application spends trying to establish a connection to the server.


The address of the server which the Uploader connects to.


The time in ms the application spends trying to establish a connection when the application is uploading chunks of data to the server.


If set to false (default) then the users cannot change the expiry date on a file. If set to true then the users can right click the file in the Upload Progress screen and change it’s Expiry Date. It is false by default because the Expiry Date does not currently get updated in integrated Telephony Providers, and hence can cause problems in some scenarios.


Used internally to allow settings to be migrated if a newer version of the application is installed. Do not change this setting.


By default this setting is true – when the application is started it checks the users temporary folder and sees if there are any upload files there, if so it checks the upload list and establishes if that file has been abandoned part way through the upload. If it is then the Uploader automatically asks the user if they wish to resume the upload. If false then the Uploader does not check.


Defines the colour used by the Uploader to show that a column of data has been mapped to a data field in the campaign Schema.


Defines the colour used by the Uploader to show that a column of data has not been mapped but is not compulsory for the Upload of the file.


Defines the colour used by the Uploader to show that a column of data has not been mapped and this column is compulsory; it must be mapped before the upload can continue.


The command used during the automated connection check test. Do not change this setting.


The delimiter used to separate columns in the generic dial file.


If true (the default) then the generated generic dial file has column headings.


The number of tries the application makes to download the generic dial file.


The number of rows the application downloads at once from the server.


By default this setting is true. If you set this to false then progress box during the file transfer stage of the Upload is presented in it’s own window.


If this is false (the default) then the application checks the central server if the current version of the Uploader is the latest version and warns the user if it is not. If true then this notification is not presented.


True by default, setting to false prevents the system generating derived data. Do not change this setting.


True by default, setting to false prevents the system from validating any data. Do not change this setting.


Defaults to, if you can’t ping this site from your client machine then change this to a reliable site which you can. It is only used for diagnostic purposes, and is not important for normal Uploader use.


Used internally do not change.


Used internally do not change.


Used internally do not change.


Used internally do not change.


Used internally do not change.


Used internally do not change.


Used internally do not change.


When a file is first opened in the Uploader it shows a wizard. This wizard has a preview of the first n lines of the data. This setting adjusts how many lines are previewed.


Do not change this setting.


This is a comma separated list of the call centre ids which you have successfully logged on to.


This is deprecated. Do not use.


This is deprecated. Do not use.


This is deprecated. Do not use.


When set to true


This is deprecated. Do not use.


Deprecated – do not use this setting.


Do not change this setting.


The colour of the ID column background in the Upload Progress window


This is the same setting as described in section "12.1.1 Number of Months Back"


Used internally. Do not change.


The background colour of row in the Upload Progress window when the file has been partially uploaded and can be resumed.


The background colour of row in the Upload Progress window when the upload is complete.


The background colour of row in the Upload Progress window when there has been a problem processing the upload file on the server.


The rate at which the Uploader Polls the server for status changes to the Upload Progress.


The default size of the chunks the uploader sends to the data to the server in. A lower number means a more reliable upload (for slower connections) but there is a fixed overhead per chunk so the higher this number the more efficient and hence quicker the transfer of data from the Uploader to the Server will be.


The number of times the uploader will retry to send a chunk of data during the file transfer.


Currently not used.


Currently not used.


If true (default) then all communication between the application and the server is encrypted. Do not change this setting.


The colour of the cell in the Uploader when the data in the cell field fails the validation rules for that column.


No used.


If true (the default) then the client compresses the upload files before transmission to the server.

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.