Help · Reading the preflight

Reading the preflight

Written for TableDI 2.0.0 on macOS · updated 2026-09-15

The preflight is the screen between dropping in this period's files and running them. It reads the files without changing anything and answers three questions: does each file match what the job expects (Does it match), what changed since last period (Against last period), and which rows will be held back for you to decide (What will be held back). A problem that makes the run impossible is listed in red under Has to be fixed before this can run, and Run this period stays disabled until it's fixed. Anything under Worth a look is a warning and never blocks.

The preflight: this period's files, what matches, what changed since last period, and what will be held back.

Files for this period

One card per source. With a folder and a file-name pattern, TableDI 2 fills in the file it expects, such as 202610_bank.csv; otherwise click Use a different file.

Does it match

Per source: how many rows were read and are usable, how many expected columns were found, columns that were renamed or are missing (a missing column comes out empty in the result), whether the key column is present, and how dates and the text encoding were read.

Against last period

Rows, New, Changed and Gone against last period's file. A big jump usually means the wrong file or the wrong month. Rows carried over from last period join this period's matching and close on their own when their pair turns up.

What will be held back

Rows with a duplicate or empty key, or an amount stored as text. After the run they wait on the job's Exceptions tab.

Has to be fixed before this can run

Each problem says what to do; the fix is on the file side. Swap in the corrected file with Use a different file and the preflight reads it again.

This period and how it goes in

The label is 2026-09 for a month, 2026-W36 for a week or 2026-09-06 for a date, and labels only move forward. How this period goes in is This period only, Add to history or Update on …; keep the job's default unless you know you need another.

Still stuck? Email us — one inbox, read by the people who build TableDI.