This guide describes the step-by-step process for importing measurements from an instrument file (CSV/TSV/TXT) into a worklist. This feature replaces manual data entry, reducing errors and saving time.
Before you begin, make sure that:
If you want to test the feature, use the demo files included in the application.
If you don't have a configured instrument, go to the Instruments page, open an instrument for editing and fill in the "File Settings" section:
| Field | Description |
|---|---|
| Delimiter | The character that separates columns (comma, semicolon or tab) |
| Encoding | File character encoding (usually UTF-8) |
| Header Row | Which row in the file contains column names (for example 1) |
| Data Start Row | Which row the measurement data starts on (for example 2) |
| Sample ID Column | The name of the column containing the sample code (for example "Sample ID") |
After saving, the instrument will appear in the import wizard list.
Go to the Worklists page and open a worklist for editing. At the bottom, below the bulk measurements table, you will find the "Import Measurements" button.
Click the button to open the import wizard.
In the first wizard step, a list of available instruments is shown. Only instruments with a configured file format (column delimiter, header row, etc.) are displayed.
Select the instrument the measurement file came from.
For testing you can use one of the pre-configured demo instruments:
| Instrument | Measurements | File |
|---|---|---|
| VELP Kjeldahl | N, N-NO3, N-NH4 | velp-kjeldahl.csv |
| Metrohm 914 | pH, EC | metrohm-914-ph.csv |
| Agilent 4210 MP-AES | Ca, K, Na, Mg, Fe, Mn, Zn, Cu, Pb, Cd, Ni, Cr | agilent-4210-mpaes.csv |
| Thermo iCAP 7400 | Ca, K, P, Fe, Mn | thermo-icap7400.csv |
After selecting an instrument, the upload area appears. You can:
Accepted file types: .csv, .tsv, .txt
The file is read immediately. The wizard uses the instrument settings (delimiter, encoding, header row) to parse the data correctly.
If the instrument has a saved mapping profile, this step is skipped automatically.
A table showing the file's columns is displayed. For each column, the wizard tries to auto-detect the corresponding analysis element. Correct mappings are marked with a green "✓ auto" label.
You can:
Click "Continue" to proceed to the preview.
The wizard compares the file's sample codes with those in the worklist. For each file row:
| Status | Meaning |
|---|---|
| ✓ Found (green) | The sample code exists in the worklist — will be imported |
| ⊘ Skip (grey) | The code doesn't exist in the worklist — will be ignored |
The "Measurements" column shows the values to be imported (for example pH: 7.2, EC: 1.85).
Review the results. If something isn't right, click "← Back" to change the mappings.
Click "Import" to start the process. The wizard:
After completion, a summary is displayed:
If there are out-of-limit values, an orange table shows:
| Element | Value | Lower Limit | Upper Limit |
|---|---|---|---|
| Fe | 285.3 | — | 200.0 |
| Pb | 12.7 | — | 10.0 |
This lets you immediately identify samples that need re-testing.
Click "Close" — the worklist's measurements table refreshes automatically with the new values.
Can I import data multiple times?
Yes. If you import again for the same samples and elements, the values are updated (no duplicates are created).
What happens with QC lines (blanks, standards)?
If the QC codes don't exist in the worklist, they are simply skipped. You can see how many rows were skipped in the results.
Do I need to map columns every time?
No — if you enable "Save profile to instrument", the mappings are saved and used automatically in future imports.
Are files with Greek characters supported?
Yes, as long as the file encoding is UTF-8 (or the encoding configured on the instrument).