Tableau Report Bursting

Automate Tableau Report Bursting for Customers and Locations

Give each customer or location its own Tableau report file. ATRS automates Tableau report bursting by running a reusable report with the approved filters and parameters for each output, then delivering the finished files.

Generate separate files for customers, stores, hotels or regions from one reporting structure.

Supply each output’s filter and parameter values from a maintained database table or query.

Choose the required PDF, Excel or CSV file and its delivery destination.

Run the location reporting job on a recurring schedule or business calendar.

The Bursting Challenge

One Report Structure. Many Different Files.

A weekly sales report may serve every store, but each manager needs a different file. As stores open or reporting requirements change, the recurring job must keep the content, filenames and destinations aligned.

Different Locations Need Different Content

North and South stores share a reporting structure. Each exported file should contain only the data its recipient is permitted to receive.

Manual Export Loops Keep Repeating

Selecting a location, exporting the report, naming the file and sending it becomes a recurring job when the audience grows.

A Saved View Is Only Part of the Job

A custom view can preserve a useful filter selection. A recurring file operation also needs export settings, destination instructions and a response when production fails.

Choosing the Right Approach

Saved Views, Export Scripts or ATRS?

Use native Tableau custom views and subscriptions when a manageable set of saved views and PNG/PDF emails meets the need. Maintained scripts can also repeat supported filtered exports. Choose ATRS Tableau report scheduler for a recurring job that combines location-specific production, chosen file formats and maintained delivery instructions.

Native views, subscriptions and scripts

Use Native Options When They Fit

Saved custom views preserve the required filter selections.

Native subscriptions deliver PNG images, PDF attachments or both.

Subscription recipients are Tableau users with View and Download Image/PDF permissions.

For occasional files, authorized manual exports may be enough.

Tableau permissions and user-based row-level security control the content available to the connected user.

A maintained export script can loop over supported filter values; your code must handle authentication, output naming, delivery and failures.

ATRS

Configure the Recurring Production Job

Repeat the selected report for the approved customer, location or region values.

Use a maintained database table or query—your driver data—to supply values for each output.

Choose PDF, Excel or CSV files and configure their filenames and destinations.

Maintain approved recipient instructions as customers and locations change.

Run the job on a regular schedule or supported business calendar.

Review exceptions, retained snapshots and results for each destination.

The export identity still matters. The Tableau account used by ATRS needs the appropriate access, export permissions and licensing. User-based Tableau row security follows that account, not a recipient’s email address. A customer or location value is an instruction to filter the output; it does not grant authorization.

From a Reusable Report to Separate Location Files

Define what changes for each output and what stays the same.

Reusable Report

Select the Tableau report and exporting account. Keep the reporting structure consistent across the location outputs.

Approved Location Values

Apply each location’s filter and parameter values, including the reporting period the file must cover.

Required Output

Choose a readable PDF, a data-oriented Excel workbook or a CSV for a receiving system. Set a distinct filename.

Configured Delivery

Send each completed file to its intended recipient or destination, then review the result.

Two Locations, Two Different Outputs

Illustrative output and delivery instructions for 5–11 October 2026. The record key identifies a driver row; the store value selects report content. Addresses and paths are placeholders, not an ATRS import specification.

Scroll across the table to see the file, route and email instructions.

Driver record	Report values	Finished file	Delivery	Email instructions
N01	Store = North; period 5–11 October 2026	north-sales-2026-10-11.pdf	SMTP email to the North manager	Subject: North sales, 5–11 October 2026. Reply-to: sales-north@example.com.
S01	Store = South; period 5–11 October 2026	south-sales-2026-10-11.xlsx	Network folder: \\reports.example\sales\South	None — folder delivery.

These filenames identify the reporting period’s end date. Add a run timestamp when retaining several versions of the same period, or deliberately use a fixed name when the folder should contain only the latest file. Choose the Excel output mode for the required rows and workbook layout.

Change the Instruction, Keep Its Identity

In the example above, N01 and S01 identify driver records. North and South are separate business values used to select report content. Keeping those roles clear makes later changes easier to review.

Update S01’s Destination

Suppose South moves its reporting folder from \\reports.example\sales\South to \\reports.example\sales\South-Review. Update S01’s destination instruction; keep its record identifier, Store = South value and reporting period unchanged.

Add the Next Approved Location

Add a distinct record such as E01 with its own approved report values, file format and route. Include it in the driver query when it is ready for recurring production.

Remove an Obsolete Instruction

Exclude S01 from future query results when South no longer needs that output. Also review fixed recipients and other schedules. This changes future selection; it does not recall earlier emails or delete delivered files.

Run N01 and the changed S01 as a representative pair. Inspect their contents, periods, filenames and destinations before expanding the job. Data-driven schedule setup.

START FREE TRIAL BOOK A DEMO

ATRS applies configured Tableau filters and recipient instructions to create personalized report files.

Give Internal and External Recipients the Files They Need

An owner, customer or partner can read a delivered PDF, workbook or CSV without opening an interactive Tableau session. External distribution must be permitted for that content.

Keep the Export Identity and Recipient Separate

Tableau access and user-based row security follow the exporting identity. Driver filters and recipient addresses do not grant authorization.

Complete Each Recipient’s Handoff

N01 uses an SMTP message and its mapped reply-to address; S01 uses a folder. Keep the chosen route alongside the file instruction so both describe the same output.

For detailed email design and sending, PDF controls, workbook preparation or CSV specifications, use the relevant guide. Delivery results and recovery explains failed handoffs.

START FREE TRIAL BOOK A DEMO

Exported PDF, Excel, CSV and report snapshots delivered to email, a network folder or cloud storage.

Size and Maintain the Recurring Distribution Job

For each run, count driver records × enabled reports × enabled destination/format combinations. Total all runs on the busiest day. Several email addresses receiving the same report instance do not multiply that count.

A Licensing Example

A run with 20 location records, one report per record and one enabled delivery/format combination produces 20 × 1 × 1 = 20 outputs. Two runs on the busiest day produce 40; add the other schedules to that daily total.

Keep Report References Current

When a Tableau report moves or is replaced, review the selected account and Item Path in each affected job. Test the updated report reference; do not assume automatic remapping.

Keep a Policy for Missing or Failed Outputs

Choose the supported blank-report response and failure notification or recovery tasks. Retain snapshots for the period required by your recovery policy.

Report-output calculation guide · Destination results and recovery.

Works with Your Tableau Reporting Environment

Install ATRS on a supported Windows host and connect to Tableau Server or Tableau Cloud. For scheduling while no user is logged in, configure the Windows Service. For database-driven jobs, set up an ODBC System DSN and give the service identity access to the driver database and destinations. Check the installation prerequisites for Office requirements relevant to advanced Excel outputs. Follow the Web Application setup guide if you want separately installed browser-based management.

✓ Tableau Server

✓ Tableau Cloud

✓ Windows-hosted scheduler

✓ Browser-based management

✓ Unattended reporting

✓ Email and file delivery

Trusted Report Automation for More Than 20 Years

ChristianSteven Software has helped organizations automate business intelligence reporting and delivery for more than two decades.

20+

Years of reporting automation experience

Nearly 5,000

Organizations helped worldwide

Countries with customer organizations

SOC 2 Type II

Independent assurance over security and operational controls

Visit Our Trust Center →

Technical Support

Get help with ATRS setup and configuration

Current Capabilities

Follow ATRS release announcements and product guides

Enhancements

Discuss your reporting requirements with the ATRS team

Report bursting produces separate files from a reusable report by applying the approved customer, location or regional values for each output. In ATRS, data-driven schedules can supply those values from database records, then generate and deliver the configured files.

Set fixed values in a schedule or map fields from a maintained database table or query to the relevant report inputs. Use the required customer or location values and reporting period. Review the resulting exports under the Tableau identity used by ATRS.

A Tableau custom view saves a useful view configuration, including filter selections. Bursting repeats file production for the required values and adds output formats, filenames and delivery instructions. Native custom views and subscriptions may be sufficient for a manageable set of PNG/PDF emails to permitted Tableau users.

No. A location or customer value selects report content; it does not grant authorization. User-based Tableau row security follows the exporting Tableau identity. That account needs appropriate access, export permissions and licensing, and each delivered file must be authorized for its recipient.

Not necessarily. The driver Key Column uniquely identifies each returned record for the data-driven schedule. A separate field can supply the business store, customer or regional value used by the report. Make both roles explicit in the driver design.

Yes. Data-driven instructions can select supported formats and destinations at runtime. Use PDF for a readable report, Excel for the required workbook or data workflow, and CSV for an agreed receiving-system file. Inspect representative outputs; the formats are not interchangeable copies of an interactive dashboard.

Yes. Native custom views, authorized manual downloads and supported export APIs can meet some requirements. A maintained script can repeat exports with supported filters; your implementation must also handle credentials, permissions, naming, delivery and failures. Choose ATRS when configuring the complete recurring file operation is a better fit.

Count data records × enabled reports × enabled destination/format combinations for each run, then total every run on the busiest day. For a fixed schedule, the data-record count is 1. Sending the same report instance to several email addresses does not multiply this count. Use the report-output calculation guide.

Evaluate the actual reports, data sources, formats, destination limits and Windows host against your busiest-day schedule. Measure whether the complete burst finishes within the reporting window and assess the corresponding output entitlement. A location count describes workload; it does not establish processing speed.

Review the selected Tableau account and Item Path in every affected schedule or package report. Test the revised references and exported content before enabling recurring delivery. Do not assume that moving or replacing a report automatically updates all ATRS references.

Use two contrasting records and inspect their files for authorized content and the right reporting period. Change one route or format while keeping its driver identifier explicit, then verify the new file and destination. Check for missing or duplicate driver records before expanding the recurring job.

Configure the supported blank-report response, retries, notifications or recovery tasks, then inspect the schedule and destination results. Enable output snapshots with a selected retention period if retained files are needed for recovery. A sent-email or upload record does not prove reading or ingestion.

Install ATRS on a supported Windows host connected to Tableau Server or Tableau Cloud. Use the Windows Service for scheduling while no user is logged in. For database-driven jobs, configure an ODBC System DSN and the service identity’s access to the driver database and destinations. Browser-based management uses the separately installed ATRS Web Application.

No interactive Tableau login is needed to read a delivered PDF, Excel workbook or CSV. The identity exporting the report still needs appropriate Tableau access, permissions and licensing, and external distribution must be permitted for that content.

Maintain the approved instruction records and confirm which records the driver query returns. For removals, also check fixed recipients, mailing lists and other schedules. Changes apply to future selection; they do not recall earlier emails or delete files already delivered.

Yes. SMTP supports a static or data-driven reply-to address, added in ATRS build 20251029. Map the servicing address and test a reply using the configured SMTP account. Reply-to does not change the authenticated sending account.