What Is Report Bursting in Crystal Reports, and How Does It Work?

Imagine a finance analyst opening a report with a section for every department. Each manager should receive only their own figures, so she exports and checks the sections individually before sending them.

Bursting automates that separation and routing. The group might be a department, branch or customer, with a destination associated with each output. The useful result is a set of correct individual documents.

It is tempting to describe every bursting implementation as one database query followed by file splitting. That is too broad. Report design, subreports and the chosen rendering method affect execution; assess performance with your actual report.

SAP Crystal Server provides personalized automated publishing with Concurrent Sessions licensing. If you already use that workflow, compare its publication result with the departmental requirement before introducing another tool.

CRD’s Bursting schedule works with groups in a report. Simple Bursting assigns destinations to selected groups; Advanced Bursting can use report fields or database lookups and assign multiple destinations and formats. The Bursting guide explains these choices.

A Data-Driven schedule takes a different approach: returned records supply report parameters and delivery instructions at run time. Use it when each department needs its own parameterized execution, rather than assuming every personalized output requires the same bursting design.

Choose two departments with clearly different figures. Confirm the RPT’s grouping expresses the separation you need, then create a Bursting schedule and select the reporting period.

Choose Simple or Advanced Bursting according to how the destination assignments are maintained. Associate the selected groups with controlled test destinations and choose the appropriate file formats. Keep the grouping value and delivery address together during review.

Open both received files. Inspect the department name, a known transaction, the total and the transition between groups. A group heading alone does not establish that detail or subreport content belongs exclusively to that department.

Then test a newly added department and a missing destination. Those are the changes the analyst would otherwise discover while preparing the monthly emails.

Bursting removes repeated exports, but somebody still owns the reporting assignments. A manager’s replacement needs the correct department, destination and any file-protection arrangements.

If an application maintains the routing data, its approvals remain part of the design. A destination lookup is an instruction, rather than an authorization decision.

The analyst should be maintaining which manager receives which figures, rather than recreating the same exports every month. Begin with the two departmental outputs you can verify confidently.

Explore CRD bursting and personalized distribution for the report structure you have. The Crystal Reports automation overview explains how distribution fits the wider reporting routine.