Skip to main content
Share / Export

Report Bursting in TERA

Bursting runs the same schedule once per row—from a SQL query or a manual grid—so each customer, job, or entity can get its own export (and email). Use this when one schedule should fan out instead of producing a single file.

When to use bursting​

  • One report per customer, vendor, job, or company from a shared .rpt.
  • Different parameter values per recipient, driven by a query or a maintained list.
  • Email To/subject/body that should change per row using {burst:FieldName}.

Skip bursting for a single fixed-parameter run—use a normal schedule instead.

Before you start​

  • The schedule’s report is saved and parameters are discovered.
  • For SQL bursting: a database connection exists and you can write a query that returns one row per run.
  • For emailed bursts: Delivery mode is Save to output folder and email, and you understand Email Delivery in TERA.
  • You understand that TERA runs Crystal reports one at a time—large bursts queue and take longer.

Open Advanced on the schedule​

  1. Open Schedules and edit (or create) the schedule.
  2. Complete Report & Output and Timing as usual.
  3. Open the Advanced tab.
  4. Check Enable report bursting.

Expected outcome: Burst source options and parameter mappings appear.

Advanced tab with Enable report bursting checked

Choose a burst source​

Under Burst source, pick one:

  • SQL rows — Query returns the list of runs at execution time.
  • Manual rows — You maintain columns and rows in TERA.

Burst source radios for SQL rows and Manual rows

Option A: SQL rows​

  1. Select SQL rows.
  2. Choose a Database connection.
  3. Enter a SQL burst query that returns one row per desired run. Include columns you will map to parameters or use in email (for example CustomerId, CustomerName, Email).
  4. Select Create Schedule / Save Changes if the schedule is new—preview requires a saved schedule.
  5. Select Preview SQL Burst Rows.

Expected outcome: A preview message with row count and field names (for example, “Preview returned 12 row(s). Fields: CustomerId, CustomerName, Email.”).

SQL burst query textarea, database connection, and Preview SQL Burst Rows button

Preview message listing row count and available burst field names

SQL tips​

  • Return only the rows you want to run—each row is a full Crystal execution.
  • Alias columns with clear names; those names become {burst:ColumnName} tokens and mapping choices.
  • If preview says to save first: save the schedule, reopen Advanced, then preview.

Option B: Manual rows​

  1. Select Manual rows.
  2. Add columns (field names) with the add-column control.
  3. Select Add Row and fill values for each run.
  4. Use the row Enabled checkbox to include or skip a row without deleting it.

Expected outcome: At least one enabled row with named columns and values.

Manual burst grid with field name columns, enabled checkboxes, and Add Row

Map burst fields to report parameters​

Under Parameter Mappings:

  1. Select Add Mapping.
  2. Choose a report Parameter.
  3. Choose the Burst field that supplies its value for each row.
  4. Optionally set a Fallback when the burst field is empty.
  5. Add more mappings for every parameter that should change per row.

Mappings override the Parameters tab defaults for each burst row.

Expected outcome: Each varying parameter has a burst field (and optional fallback).

Parameter Mappings section with Parameter, Burst field, Fallback, and Add Mapping

If burst field dropdowns are empty:

  • SQL: Preview SQL burst rows first (after saving).
  • Manual: Add at least one column name in the grid.

Use burst fields in email​

  1. On Report & Output, choose Save to output folder and email.
  2. On Delivery, set To/CC/BCC/subject/body using burst tokens such as {burst:Email} or {burst:CustomerName}.
  3. Keep Attach exported file to email checked if each recipient should get their file.

Each burst row sends its own email with tokens resolved for that row.

Delivery tab To field using a burst email token from the variable menu

Save, test, and monitor​

  1. Save the schedule with bursting enabled.
  2. Select Run / Run Now for a controlled test (start with a small SQL filter or few manual rows).
  3. Watch Run History—you should see multiple runs or a burst series depending on how history is recorded for the job.
  4. Confirm output files and emails per row.

Run History after a burst test showing multiple related outputs or run entries

Performance and limits​

  • Only one Crystal report executes at a time. A 50-row burst is fifty sequential runs.
  • Preview early and keep test queries small.
  • Filename templates still apply per run—include tokens that keep files unique if they share a folder.

Common mistakes​

  • Preview before save — SQL preview requires a saved schedule.
  • No parameter mappings — Every row may reuse the same Parameters tab defaults.
  • SQL returns too many rows — Accidental full-table bursts can run for hours.
  • Manual rows with blank field names — Name columns before mapping or using {burst:...}.
  • Email tokens for fields not in the query/grid — Preview or column headers must expose the field name.
  • Expecting parallel execution — Bursting is sequential by design.

Next steps​

  • Email Delivery in TERA — Full token and SMTP reference.
  • Monitoring and Troubleshooting TERA — Partial burst failures and logs.