Using Existing Automation Scripts to Import Your Data (No Coding Required)

Audience: Lab users / scientists with no programming background

Goal: Use an existing ETL script to import data into a Data Template.

Learn how to use an existing ETL automation script to turn a raw export (Excel, CSV, TXT, …) into clean, mapped data in your Data Template — without writing any code.

In Albert, an ETL automation script is a small program that knows how to read a specific export format and fill your Data Template for you.

• Reads your exported data file (Excel, CSV, TXT, …).

• Cleans and reshapes it (for example, converts commas to dots, removes extra rows).

• Fills the columns of your Data Template automatically.

You do not have to write code. You only:

1. Select the correct ETL script for your Data Template.

2. Upload the correct exported file from your instrument or software.

3. Confirm the “Map fields to import data” step and finish the import.

Use an ETL automation script when:

• You always export data from the same instrument or software.

• The exported file always has the same structure (same columns, same layout).

• You want to avoid manual copy/paste and reduce mistakes.

If your file changes every time (columns move, new tabs, extra sheets), talk to your admin or data owner before using automation. The script may need an update.

Before you start, make sure you have:

• A Task with a Data Template that is configured to use an ETL script.

• The correct export format from your instrument or analysis software.

• The right script selected for this Data Template (your admin will usually configure this).

1. Open your Task.
   Go to the Task where you want to upload results and open the Results / Block where the Data Template is attached.

2. Start the data import.
   Click Import data. If the Data Template is already linked to a script, you will see a note indicating that an ETL automation script will run.

3. Choose your file.
   Click Upload file, select the exported file from your instrument (Excel / CSV / TXT), and confirm.

4. Let the script run automatically.
   Albert runs the ETL script in the background. The script reads your file, cleans it, and prepares the data for your Data Template.

5. Review “Map fields to import data”.
   You will see a page called “Map fields to import data”.
   The columns shown here are the result of the ETL script. In most cases, the mapping is already correct because the script is written to match your Data Template.

6. Review the table.
   Check that:

   • Each row corresponds to a correct sample, batch, or measurement.

   • Each column has the right values (for example, “Viscosity (10 s-1)” really contains viscosity at 10 s⁻¹).

   If something looks wrong:

   • Stop the import.

   • Contact your data or automation owner with:

     • The file you used.

     • A screenshot of the mapping screen.

     • A short description of what you expected.

7. Finish the import.
   Click Submit to complete the import.
   The data is now stored in the Task, ready for analysis and reporting.

   

⚠️ If something doesn’t look right: don’t “Submit” just to see what happens. Cancel the import and share your file, the error (if any), and screenshots with your automation owner so they can safely adjust the script.

Quick answers to common questions for lab users who rely on ETL scripts but don’t write them.

Some Data Templates are configured without scripts. In that case, you can still import data manually by mapping file columns directly on the “Map fields to import data” screen. If you think this Template should have a script, ask your admin or data owner.

This usually means the structure of the file doesn’t match what the script expects (for example, a column was renamed or removed). Send the exact error text and your file to the internal person who maintains the scripts so they can adjust it.

If you’re not a programmer or admin, please don’t try to edit scripts yourself. Instead, provide a sample file and a short description of what each column means to your automation contact so they can update the script safely.

Need more help with ETL automation scripts? Contact support.