Can Tableau’s Export All Extension Run Automatically on a Schedule?

The Tableau Exchange listing describes a dashboard button, selected sheets and columns, and a single Excel download. The developer’s public project documents the interactive setup and describes summary-data export. Neither documents a built-in unattended scheduling and email service for this workflow.

If the extension is unavailable to interactive users, ask the Tableau administrator to review its network-enabled extension approval and site policy. That access issue is separate from configuring recurring delivery. Do not assume enabling the extension creates a scheduler.

Use the existing file to confirm fields, aggregation, filters and period for each report. An alternative export route must be checked against that requirement; it should not be presented as automatically reproducing Export All’s workbook or configuration.

The Package Schedule guide covers report selection, destinations, Excel/PDF merging and exception handling at report and package levels. Excel merging retains formatting and style. Check each member and the final combined file, including how the job responds to missing required content.

The Excel guide covers worksheet names, workbook passwords, file properties and naming. Data Only supports a template worksheet with a specified or next available row/column, selected row/column totals, reusable styling and header-based data types and custom formats. Test formulas, changing row counts and any old cells around inserted data.

Related Files & Folders tasks can merge existing Excel files or change a workbook’s password, read-only setting and file summary. Build Excel Workbook creates a file from database queries and datasets; it is separate from exporting Tableau reports.

Use clear filenames and date/time suffixes for recurring outputs. ZIP password protection, configured PGP encryption and deferred delivery are available preparation choices where appropriate. Check the current host and 64-bit Office prerequisites for advanced Excel output.

For personalized packs, the Data-Driven Package guide covers grouping and merged PDF or Excel delivery. Grouped package outputs are attachments rather than embedded report bodies. Verify the intended audience and file for each sample.

ATRS supports Tableau Cloud only. It does not schedule a click on Export All or automatically import the extension’s selected sheets and columns. Configure the equivalent reporting requirement and test it through ATRS’s own output and delivery route.

Find the intended package and its actual UniqueId through the documented folder and package discovery operations. This example uses ScheduleType: package for an ordinary report package. Replace 101 with its stored identifier, use your ATRS HTTPS address and keep the token on the backend.

POST /api/Schedule/ExecuteScheduleAsync
Authorization: Bearer <ATRS-access-token>
Content-Type: application/json

{
  "ScheduleType": "package",
  "UniqueId": 101,
  "RunBy": "Finance application"
}

GET /api/Schedule/GetExecutionStatus?ExecutionId=<returned-id>
Authorization: Bearer <ATRS-access-token>

Authorize the caller for this finance package. Save the returned ExecutionId, poll within a defined time limit and parse the JSON-encoded ResultJson. Completed can contain Result=false. Check every required report and the destination, rather than treating a finished execution as proof of a complete workbook.

The request runs the package’s saved report inputs, merge and delivery settings. It does not invoke Export All, supply a new reporting period or return the workbook bytes. Configure assembly through the supported ATRS workflow unless the API explicitly documents the setting you need.

For a data-driven package, use its actual stored family and documented execution contract. After an uncertain response, inspect the execution and destination before resubmitting to avoid duplicate deliveries. See asynchronous execution and monitoring and delivery verification.