How Do You Burst Tableau Reports for Different Customers or Locations?

Imagine the sales coordinator preparing the weekly update for a growing group of stores. Each manager wants their own sales, with the completed week selected. The coordinator repeats the same export, changes the filename and chooses the next address.

Report bursting makes that repeated selection and delivery into a maintained reporting job. One reusable Tableau report can supply the different versions, while ATRS reads the store and delivery instructions from a database table or query.

That is useful for customers as well as locations. The instruction for each output can identify the approved report values, person, format and destination. The goal is a manager opening their own figures, rather than the coordinator working through another morning of attachments.

Begin with the assignment that connects a location to its reader. A recipient’s address routes a file; it does not by itself filter the Tableau data.

Each report’s store selection and delivery details stay together, even when every version starts from the same published report.

For a few stable management snapshots, Tableau Custom Views and native subscriptions may be enough. Save the intended store selections and maintain the appropriate subscription audience.

The work grows when managers move, stores open or finance asks for a different output. ATRS data-driven schedules can read those changing reporting assignments when the job runs, rather than require a separate manual export for each request.

One manager might receive a PDF by email while a local analyst needs an Excel workbook in a reporting folder. The useful choice follows what each person does with the figures, and the maintained record keeps that choice beside their store.

Choose two managers whose store totals you recognize. Agree the weekly report, store values, test destinations and filenames with the person maintaining those assignments.

Create the ATRS Data-Driven Schedule and connect its driver to the maintained query. Select the Key Column, Tableau Cloud account and report, then map each record’s store and reporting period to the supported inputs.

Map the destination and naming fields so the two versions remain recognizable. If a reader needs a prepared workbook, include the useful tab name, template and number formats in that output instead of leaving finance to repeat the finishing work.

Open both received files with the reporting owner. Compare each store, period and known total, and verify that the destinations match the assignments. Change one test assignment and confirm how the next selection follows it before enabling the wider weekly list.

The Data Driver defines the reporting records used by ATRS. Use your maintained store and delivery instructions in place of the pictured sample query.

A store portal may let a manager request another copy before a review. Its backend can select the approved ATRS job while the reporting team maintains the report inputs and destination.

For a small setup, a tested single-report schedule for each store makes that choice explicit. Broader data-driven jobs need their own deliberate execution scope.

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

{
  "ScheduleType": "report",
  "UniqueId": 101,
  "RunBy": "Store portal request"
}

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

The next weekly review can start with each manager’s own sales file. The coordinator can help explain the results instead of selecting another store and rebuilding another email.

Start with two recognizable locations and their reporting assignments. Use that pair to explore how ATRS can extend the same useful report across the audience.

Explore ATRS report bursting