Export & distribution | ATX AnalyticsTable Handbook

Export & distributionOne dialog, every destination — and the whole configuration is schedulable. Export is deliberately one dialog reachable with any destination pre-selected. Sources are the active grid, the current query result, a selected or typed range, or a table read straight from a connection. Destinations run from an .xlsx download through flat files on a folder path or in cloud storage, to a table in DuckDB, PostgreSQL or BigQuery — overwrite or append. Every option, including multi-sheet composition, can be handed to the scheduler as a single configuration.

What it does

Sources: active grid, current query result, a selected or typed range, or a table from a connection
Destinations: .xlsx download, flat file (CSV/TXT/.xlsx) to a folder or cloud bucket, or a database table in DuckDB, PostgreSQL or BigQuery
File options: delimiter, header row, encoding (UTF-8 with or without BOM, UTF-16 LE/BE, Windows-1250/1252, ISO-8859-2) and line endings (CRLF/LF/CR)
Multi-sheet workbooks composing several objects into one .xlsx, each with its own sheet name, placement anchor, header toggle and header/row formatting
Parameters in folder and file names, resolved at run time
Cloud copy for moving finished artefacts between storage locations

How it works

Choose the source, choose the destination, set the file options, and either run it now or press Schedule this export.
Encoding and line endings are explicit because the receiving system usually cares and rarely says so.
Multi-sheet composition places each object at its own anchor, so a workbook can carry a summary, a detail table and a reconciliation on separate sheets.
The full definition is mirrored to the project's Export folder as JSON and re-synced on every change and on save.

Practices that keep it reliable

Pin the encoding for any downstream system you do not control — UTF-8 with BOM is the usual answer for Windows desktop tools that would otherwise mangle accented characters
Put the date in the folder name rather than only the file name; a year of daily files in one folder becomes unmanageable
Export to a database table rather than a file whenever the consumer is a system rather than a person

In a regulated environment

Because the export definition is a reviewable JSON file, a change to what leaves the organisation is a diff rather than a discovery.
Configurable file-size limits in Settings stop an accidental full-table export from filling a share.

Screens

Export — one dialog, reachable with any destination pre-selected.
Multi-sheet workbooks — several objects into one .xlsx, each with its own sheet and formatting.
Flat files — delimiter, encoding and line endings made explicit, not assumed.
Database destinations — write into DuckDB, PostgreSQL or BigQuery, overwrite or append.
Cloud copy — move finished artefacts between storage locations without a local round trip.

ATX Institute on LinkedIn

This site needs JavaScript for the full experience. Every page above is reachable without it.