Crystal Reports Delivery
Put the Report Where the Work Happens.

Put reports in the shared libraries, folders and printers your teams already use. CRD handles recurring delivery and helps you see when a job needs attention. All features are included in your licence, with no paid feature add-ons.
Route reports into the required SharePoint site and folder.
Deliver to network folders, printers and supported cloud destinations.
Use several destinations in the same reporting schedule.
See failed deliveries and recover the work.
The Delivery Challenge
The Report Is Only Useful When It Reaches the Right Place.
The office needs a copy in SharePoint. The warehouse needs a printout. Another team needs a file on SFTP. CRD keeps those destinations with the reporting schedule.
Teams Work in Shared Locations
A report may belong in a business folder, library or location printer.
The Location Can Change
Sites, folders, file names and metadata may depend on the customer or reporting group.
A Missing File Creates More Work
Your team needs to see what failed and know what to do next.
Why Choose CRD
Reach More of the Places Your Teams Work
CRD adds current SharePoint routing, cloud storage and team destinations to the recurring reporting job.
SAP Crystal Server
Established Delivery Routes
SAP Crystal Server supports file-system, FTP and SFTP delivery as well as email and printing.
SharePoint integration depends on the version and method. A legacy network-path integration is different from delivery into a current SharePoint Online site.
CRD
More Destinations, With Delivery Visibility
Use dynamic SharePoint sites and folders, with document metadata.
Save to network folders or print where the work happens.
Deliver to Teams, Slack, Amazon S3 and Azure Blob.
Use several destinations in one schedule.
Find failed runs and use retained output where a resend is appropriate.
Delivery and data-driven routing are included at no additional feature cost.
One Reporting Run. Two Required Destinations.
For example, the same management pack belongs in a network folder and a SharePoint library. CRD can deliver both from one reporting run. If one destination fails, your team can investigate that handoff.
Prepare
Run the reports for the pack.
Route
Send to both destinations.
Inspect
See the result of each handoff.
Recover
Resend retained output or rerun as needed.
Send Reports Where People Look for Them
Keep delivery with the report schedule, instead of moving the files yourself.
SharePoint Sites and Libraries
Place reports in SharePoint sites and folders, with the document details your team uses.
Folders, Transfer Servers and Printers
Use disk, network folders, FTP, FTPS, SFTP or a receiving team’s printer.
Cloud Storage and Team Workspaces
Reach Google Drive, OneDrive, Dropbox, Amazon S3, Azure Blob, Slack and Teams. Google Sheets delivery uses Google Sheets output.
When a Delivery Needs Attention
Give the people responsible for reporting useful information and a way forward.
Skip Empty Reports
Avoid sending a blank report when there is nothing to share.
See What Went Wrong
Use execution, retry and history views, with email or supported SMS alerts.
Keep a Copy for Recovery
Retain snapshots and recent output for later review or an appropriate resend.
Share Responsibility Clearly
Control which reporting functions each operator can use and keep records of supported activity.
Try the Route Your Reports Need to Take
Use the free 30-day trial with a report and the site, folder or printer your team relies on. See the file arrive, then explore how CRD helps when a delivery needs attention.
Built by ChristianSteven Software
Reporting automation experience from organizations around the world.
Your Report Delivery Questions, Answered
Answers to common questions before you try CRD.
Yes. A schedule can use several destinations with their own output and delivery settings. Delivery and data-driven routing are included at no additional cost.
Current CRD builds support dynamic SharePoint URLs and folders with metadata options. The account still needs the tenant consent and permissions for those locations. Data-driven routing is included in the licence.
CRD provides retained-output and resend options within their supported scope. The output must still be available and suitable for the resend.
Blank-report rules and delivery exceptions have separate responses. The run history helps your team decide whether to resend retained output or rerun the job after partial success.
Yes. Deferred Delivery can generate output at the scheduled time and hold delivery until later. It applies to scheduler runs.
No. Sending and destination records help investigate delivery; they do not establish that someone read or understood the report.
Show Us Where Your Teams Need Their Reports
Bring a report and the places it needs to reach. See how CRD can handle the recurring delivery and help your team when a run needs attention.