How to Put Crystal Reports Results in an Email Body

Imagine an operations manager checking a short daily exceptions report on her phone. The PDF contains only a few lines, but opening an attachment adds another step before she can see whether anything needs attention.

An inline report can make that brief update easier to read. Keep the PDF or workbook when the recipient needs a complete document, a durable working file or more detail than the email should carry.

Start with a short report whose values and headings are easy to recognize. A long, page-oriented layout is unlikely to become a good email simply because it is embedded.

A custom workflow can export report content to HTML and build an email around it. That leaves the implementation responsible for images, styling and the way different mail clients render the message.

CRD’s Email destination provides Embed Report and an optional Include Attachment setting. HTML embedding requires SMTP; MAPI messaging supports embedding in text format only. In a Data-Driven schedule, Group reports by email disables report embedding.

CRD also documents an optional AI-generated report summary, introduced in build 20260304. A generated summary is different from embedding the report itself and should be reviewed for the intended reporting use.

The Email destination guide explains embedding, attachments and summary settings.

Select the short exceptions report and configure the intended day and recipients. In the Email destination, write a subject that identifies the update and choose the configured SMTP connection for HTML embedding.

Enable Embed Report and review its output options. If the manager also needs a separate document, enable Include Attachment and choose the required attachment format. Use message Inserts where a changing period or value belongs in the accompanying text.

Send a controlled test and view it in the mail clients the manager actually uses. Check headings, values, images and the optional attachment. The report must remain understandable on the small screen where she first reads it.

Forwarding or replying can change HTML presentation, so check that behavior if it is part of the normal handoff. Keep an attachment when colleagues need a more stable document alongside the quick view.

If you use the optional AI summary, configure the supported account, model and usage settings. Establish who checks whether the summary preserves important exceptions; the generated wording should not silently replace the report’s figures.

The morning email should make the exceptions visible without making the manager hunt for the answer. Keep the presentation short and retain the file she needs for a closer look.

Explore CRD email automation using one report suited to reading inside the message.