pbPassingBI
/
Publishing & outputs beginner 6 min

Output steps

Where a flow ends up, and which output type to choose.

What you'll be able to do
  • Configure the output types
  • Choose between replace and append
  • Output to several destinations from one flow

Output types

TypeUse for
.hyper extractLocal file for Tableau Desktop
Published data sourceShared on Server or Cloud — the usual choice
CSV / ExcelHanding data to other tools or people
Database tableWriting back to a warehouse

Published data source

The most useful output for a team. The flow writes to Server or Cloud, and every workbook connecting to that data source gets the refreshed data.

That gives one prepared, governed data source rather than each analyst preparing their own — which is normally the reason to adopt Prep at all.

Write options

For file outputs: Create table replaces, Append to table adds rows.

Append duplicates on rerun

Append adds every row again each time the flow runs. Unless the flow only ever processes new rows, use create/replace.

For database outputs there is also Replace data, which keeps the table structure and permissions while swapping the rows — usually better than dropping and recreating.

Several outputs

One flow can have several output steps on different branches: a full detail extract, an aggregated summary, and an exceptions file of rows that failed a join.

That last one is worth building as a habit — rows dropped by a join should go somewhere a person can see them rather than vanishing.

Field naming

The output is what analysts see in Tableau. Rename fields to what a business user would call them — Revenue, not rev_amt_usd — and remove anything nobody needs.

A prepared data source with 200 cryptic fields is barely better than the raw table.

Key points
  • A published data source gives the team one governed, refreshed source
  • Append duplicates data on every rerun — prefer create or replace
  • Rename fields for the people who will use them, not for the source system
Check yourself