Output · Files
Write Daedalus Table
Saves the table with its column formats into one .ddtable file, so a colleague can pick it up in another project and see it printed the same way.
Also known as: Hand-off, snapshot
How it works
Type the Daedalus table file name (output.ddtable by default) and pick a Location; blank means the project folder. The node writes the table together with the column formats that Format Table nodes set upstream, such as currency, date patterns, decimals and rules, so a Daedalus Table Reader in another project prints the columns exactly the same way. The write fails if the file already exists unless you tick Overwrite if the file already exists. The file is a DuckDB database underneath, so other tools can open it, but for data handed to tools outside Daedalus use Write Parquet or Write CSV. The written file is passed on downstream as a File.
Inputs and outputs
Inputs
data— Table
Outputs
file— File
Settings
The Attributes panel of Write Daedalus Table, as in the app: the controls work, but nothing runs — there is no data behind it.
The same settings, as the Assistant writes them
{
fileName: string
directory?: string
overwrite?: boolean
}writes a .ddtable file: the table plus the column formats set by Format Table nodes upstream, so a Daedalus Table Reader in another project prints the columns the same way. Use it to hand a half-built pipeline to a colleague; use Write Parquet/CSV for tools outside Daedalus.
Example
You prepared and formatted a sales table and a colleague will build the report in their own project. Name the file sales-prepared.ddtable, tick Overwrite if the file already exists, and send them the file; their Daedalus Table Reader picks it up with the formats intact.