Crystal Reports Automation API

Automate Crystal Reports From Your Application.

Let your application initiate the reporting job while CRD prepares and delivers the finished output. Connect your business process to configured report production, customer packs and delivery. All CRD functionality is included in your licence, with no paid feature add-ons.

Run an existing reporting job from your application.

Create and maintain supported schedules and reporting choices.

Prepare packages and customer-specific output.

Follow the execution and verify the delivered result.

The Application Reporting Handoff

Billing Has Finished. Reporting Should Follow.

When your application finishes a business transaction or reporting cycle, the required reports still need to be produced and delivered. CRD supplies reporting operations your application can integrate.

Select the Right Job

The application must choose the approved report or package for that business event.

Use the Right Customer Instructions

Parameters and permitted recipients need to follow the application’s business rules.

Complete the Delivery

A request is only the beginning of the reporting work the business needs.

Why Choose CRD

Connect Your Application to a Configured Reporting Workflow

Choose CRD when you want to integrate the reporting operations behind the finished customer file or pack.

SAP Crystal Server

Crystal Server Integration Components

SAP Crystal Server provides .NET, Java and web-services integration components alongside its reporting platform.

Available operations depend on the report type, installed version and publishing entitlement.

CRD

Reporting Work Available to Integrate

Schedule management: discover and maintain the supported reporting jobs.

Reporting choices: update parameters and supported single-report email destinations.

Packages: select the Crystal reports and applicable PDF or Excel merge settings.

Bursting: use the dedicated report-column, group-value and schedule-creation workflow.

Execution visibility: follow API runs and use the applicable operator controls.

API, package, bursting and data-driven functionality is included in the CRD licence at no additional feature cost.

From a Completed Billing Cycle to a Customer Pack

For example, your billing application finishes an approved cycle and requests the configured customer reporting job. CRD produces the report or pack and sends it through the configured delivery route.

Authorize

Your application selects the job and reporting context the caller is permitted to use.

Request

Initiate the existing report or package through the CRD API.

Follow

Track the returned execution status and review the final result.

Confirm

Inspect the customer’s finished output at the intended destination.

Keep Business Rules in Your Application. Let CRD Run Reporting.

Connect your backend to the installed CRD API Service and integrate the reporting operations that fit your process.

✓

Use the Reports Your Business Already Relies On

Start with representative Crystal reports, their required data access and the unattended reporting configuration.

✓

Produce the Complete Customer Pack

Create applicable packages or data-driven packages containing the chosen Crystal reports. Package and data-driven functionality is included in the CRD licence at no additional feature cost.

✓

Follow the Reporting Work Through Delivery

Use returned execution status to follow an API run, then verify the actual destination. Request acceptance, execution completion and confirmed delivery are separate checks.

START FREE TRIAL BOOK A DEMO

CRD processes application requests into report packs and delivery results

Make Each Application Responsibility Clear

Use CRD for the reporting workflow while your application controls the business request and the experience around it.

The Business Decision

Authorize the caller and select the report, permitted data and recipient context before requesting reporting work.

The Saved Reporting Job

Maintain or import the compatible CRD job definitions your workflow needs. Changes to a saved job persist, so design how concurrent requests share or separate schedules.

The Reporting Services

Run the installed API Service and CRD Scheduler with the report runtime, data connections and service access your configuration requires.

The Finished Result

Use the configured delivery route. If the application needs to present a file for download, build and authorize that file-access experience separately.

Yes. Discover the authorized schedule and use its applicable execution operation, then follow the API run’s returned status and inspect the destination. The API Service and CRD Scheduler must be running.

Supported single-report operations include creation, retrieval, cloning, renaming, enabling, disabling and deletion. Parameter and email-destination changes use their own supported operations. Verify the exact schedule type and installed-build contract.

Yes. The package operations support collections of Crystal reports, data-driven settings and applicable PDF or Excel merge options. Use the operation for the package or package schedule you need. These CRD features are included in your licence at no additional feature cost.

Yes. CRD documents a separate workflow for report columns, group values and bursting-schedule creation. Bursting is included in the CRD licence at no additional feature cost. Validate the required report and recipient scope during evaluation.

The API provides execution status, queue and capacity information, plus applicable cancellation and termination operations. Cancellation and termination have different effects and belong in an authorized operator procedure. Check the resulting state and actual delivery rather than assuming a control request completed the business job.

Do not assume so. An update changes a saved schedule. Your application needs a design for schedule ownership, concurrent requests and customer data isolation, including when to use separate jobs.

An execution response is not an automatic report download. CRD uses the configured delivery route. If your application needs a download experience, build and authorize the corresponding file-access route.

Use the supported CRD version and the operation contract for each schedule type. Confirm report runtime, database access, unattended execution and API authentication, then test the finished output and delivery with your application.