Crystal Reports Automation API
Automate Crystal Reports From Your Application.

Your application knows when the customer’s report is needed. Let CRD handle the reporting work: run the reports, prepare the pack and deliver the files. All features are included in your licence, with no paid feature add-ons.
Run an existing reporting job from your application.
Manage schedules, parameters and supported email settings.
Prepare packages and customer-specific output.
Track the reporting run from your application.
The Application Reporting Handoff
Billing Has Finished. Reporting Should Follow.
The billing cycle is complete, but the customer still needs a statement and supporting reports. Connect your application to CRD so that reporting can follow the business transaction.
The Right Reports
A customer may need a statement, a detailed breakdown or a complete pack.
Their Reporting Choices
Dates, customer values and recipients need to follow your application’s rules.
Less Reporting Code to Maintain
Preparing files, assembling packs and managing delivery all add work around report generation.
Why Choose CRD
Connect to Reporting Work You Can Configure in CRD
Use the API to reach CRD’s schedules, customer-specific reports and package preparation from your application.
SAP Crystal Server
Crystal Server Integration Components
SAP Crystal Server provides .NET, Java and web-services integration components alongside its reporting platform.
Operations depend on the report type and version. Personalized Publications require Concurrent Sessions licensing.
CRD
Reports, Packs and Delivery Behind Your Application
Discover, create and maintain supported reporting jobs.
Update report parameters and supported single-report email settings.
Build packages with the selected reports and supported merge options.
Use CRD’s dedicated bursting operations.
Start runs and follow the returned execution status.
API, packages, bursting and data-driven reporting are included in your CRD licence. No additional publishing feature licence is needed.
From a Completed Billing Cycle to a Customer Pack
For example, a billing application finishes the month’s invoices and asks CRD to run a customer pack. CRD produces the reports and sends them through the saved delivery settings.
Authorize
Select the customer’s permitted reporting job.
Request
Ask CRD to run it.
Follow
Track its execution status.
Confirm
Use the delivery records and destination to confirm the result.
Keep Your Business Rules. Hand Over the Reporting Work.
Your application decides who can request what. CRD supplies the reporting operations behind the request.
Use the Reports Your Business Already Relies On
Work with the Crystal reports your business already uses.
Produce the Complete Customer Pack
Let CRD assemble reports for the customer through packages or data-driven packages, included at no additional cost.
Follow the Reporting Work Through Delivery
Track returned execution status. Delivery records and the destination provide the next part of the picture.
A Clear Division of Work for Your Developers
Build the customer experience around reporting jobs maintained in CRD.
Your Application
Own user permissions, customer data choices and the request.
CRD’s Reporting Jobs
Maintain the report settings, parameters, pack assembly and delivery.
Your Reporting Installation
Run the API Service and Scheduler with the runtime and data access your reports need.
The Customer Experience
Add any portal, viewer or file-download experience your application needs.
Connect One Business Event to a Real Report
Try CRD free for 30 days with a report your application needs to request. Follow it from the application through CRD to the finished file or customer pack.
Built by ChristianSteven Software
Reporting automation experience from organizations around the world.
Your Application Integration Questions, Answered
Answers to common questions before you try CRD.
Yes. Use the schedule’s execution operation and follow the returned status. The CRD API Service and Scheduler must be running.
Supported single-report operations include creation, cloning, renaming, enabling, disabling and deletion. Parameters and email-destination updates have dedicated operations. Availability depends on the schedule type and installed build.
Yes. The API includes package, data-driven package and dedicated bursting operations. All these features are included at no additional cost.
Use execution status and the available queue information. An accepted request or completed run is distinct from confirmed delivery; use the delivery records and destination for that final check.
A parameter update changes the saved schedule. Your application must coordinate concurrent requests or use separate jobs where needed to keep customer reporting separate.
The execution response is not an automatic file download. CRD uses the saved delivery route. Your application supplies and authorizes any file-download experience.
Show Us What Happens After Your Application Says “Ready”
Bring the business event and the reports customers need next. We’ll show you the reporting work CRD can handle behind it.