Can One Tableau Reporting Job Deliver Different Formats to Different Destinations?

Imagine the operations analyst finishing the weekly service report. Managers want a PDF to read before the meeting. Finance needs the rows in Excel, while the service system expects a CSV in its import folder.

All three requests begin with the same reporting requirement, but their deliverables are different. Repeating the exports by hand leaves more opportunities for a period or filename to be changed in only one place.

ATRS can maintain the report inputs and several destinations, with the output format selected for each. The weekly job can serve the meeting, reconciliation and system handoff without leaving the analyst to rebuild every delivery.

Conceptual illustration: Report files routed to the people and locations that use them.

Keep the simple route when one Tableau image or PDF subscription serves the whole audience. It is useful precisely because there is little else to prepare.

The balance changes when the recipients work differently. Finance’s workbook may need a template, tab name, totals and column formats before it is useful. The system’s CSV may need a particular separator and stable filename. Managers need a readable document with the week clearly identified.

Give each destination one of those jobs. An archive copy can preserve the period’s reports, while a working folder supplies the current import. When several source reports belong together, use a package rather than stretch one report into an unrelated set of requirements.

Start with one completed service week and test destinations for all three readers. Select the Tableau Cloud report in ATRS and supply the period that each file must represent.

Add the manager’s Email destination with PDF output. Add the finance destination and choose the Excel output and preparation it needs, then configure the CSV destination around the service system’s accepted sample.

Run the job and open each received file with its owner. Compare a familiar service record and the agreed total, then let finance use the workbook and the system owner import the CSV. Matching filenames alone cannot show whether each handoff works.

Try one destination being unavailable and discuss the recovery. The PDF might have arrived even if the folder transfer failed. Once the team understands those outcomes, enable the recurring job with a clear owner for exceptions.

The Destinations step keeps the reporting job’s delivery locations together. Configure each output for the reader or system using it.

Your operations application may request another weekly handoff after a correction. It can run the saved ATRS job with its maintained outputs and destinations.

The application needs to follow all expected outcomes before saying the reporting work is complete.

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

{
  "ScheduleType": "report",
  "UniqueId": 101,
  "RunBy": "Weekly service reporting"
}

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

The managers can read the service review, finance can reconcile its workbook and the system can consume its CSV. The analyst can use the morning to discuss an unusual service result rather than repeat the same exports.

Bring the three files people currently prepare from one report. They give you a practical starting point for a maintained ATRS delivery.

Explore ATRS multi-destination delivery