CRYSTAL REPORTS QUESTIONS

How Can I Email Each Group in a Crystal Report as a Separate PDF?

Use a bursting workflow that associates each report group with its own PDF and email destination. Confirm the document’s contents as well as the address before enabling delivery.

CRD’s Bursting schedules can keep group selection, PDF preparation and recipient routing together.

  
The customer statement

Send the right attachment without exporting every group

Imagine preparing statements from a report grouped by customer. You can see all the statements correctly in Crystal Reports, but exporting and attaching each customer’s pages turns a finished report into another afternoon’s work.

The requirement is one PDF for each customer and an approved address for that PDF. Page numbers alone are a fragile routing rule when a customer’s statement grows.

For this example, use the customer group as the boundary. Keep two customers whose transactions are easy to recognize for your first test, so you can see whether the output really separates them.

Do not start with the full audience

Route the initial files to controlled mailboxes. You need to inspect the attachments before customers see them.

  
Your options

Email Crystal Report groups as PDFs for each customer

If SAP Crystal Server personalized publishing is already configured and licensed through Concurrent Sessions, it may provide the required customer PDFs. Compare its recipient report and publication output with this statement job.

In CRD, Simple Bursting lets you select a group and assign its destination. Advanced Bursting can obtain addresses from fields in the report group or a database query, useful when the list changes.

A Data-Driven schedule is appropriate when each customer statement should be generated with its own report parameter. That is a valid alternative to grouped-report bursting. The CRD Bursting guide and Data-Driven guide explain the separate workflows.

Keep the document boundary explicit

One email with every customer PDF is not the requirement. Review how each group becomes its own intended attachment.

  
Set it up

Build the two-customer PDF delivery

Create the Bursting schedule, choose the grouped RPT and set the reporting period and database access. Select the customer group and the appropriate bursting mode.

For the first customer, configure an Email destination and PDF output. Map the approved recipient, then give the message and filename enough context to identify the statement period. Repeat for the second customer or configure the documented field-driven routing.

Send the controlled run and open both attachments. Check customer identity, transactions, totals and all pages, including any subreport. Verify that one customer’s final page has not become the next customer’s first attachment.

Once the files are correct, test a changed address and an absent destination. If the PDFs need an opening password, agree the password process and test the delivered file before moving to live recipients.

Use a recognizable filename

A customer identifier and reporting period help the recipient find the statement later. Avoid unnecessary personal information in filenames.

  
Keep it dependable

Make a missing statement visible without sending duplicates

The recurring job should relieve you of exporting each statement, while leaving a clear way to investigate the one customer who reports a missing email. Keep the customer assignment with the run record.

A mail server accepting a message is one milestone. It does not establish that the customer opened the intended attachment.

Technical reference: group content and partial delivery

Advanced Bursting can use group fields or a database lookup for destination values. Confirm those values describe the intended customer and that the report selection and subreports preserve the same boundary.

Use the schedule’s history and destination evidence before repeating an uncertain run. Check which statements were already sent; email delivery is not guaranteed exactly once, and bursting does not establish a universal single-query implementation.

Try a statement with several pages

A short sample can hide a boundary problem. Include a customer whose statement spans more than one page.

  
Your next step

Let each customer receive a statement ready to use

The customer opens their own statement and accounts keeps an understandable delivery assignment. You no longer need to repeat the same export-and-attach sequence for every group.

Use CRD personalized distribution with your grouped statement, or explore Crystal Reports automation for related packaging and delivery requirements.

Contributors:

Christian Ofori-Boateng

Christian Ofori-Boateng

CEO, ChristianSteven Software