Crystal Reports Customer Portal
Let Customers Request Reports From Your Portal.

Give customers a way to request statements and recurring reports from the portal they already use. Your team connects its existing portal to CRD, which prepares and delivers the reports. All features are included in your licence, with no paid feature add-ons.
Let customers choose from the reports they can access.
Accept their reporting period and delivery choices.
Request an individual report or customer pack.
Show the reporting run’s returned status.
A Familiar Customer Request
“Could You Send My Statement Again?”
Your customer is already signed in to the portal. They should be able to request an available statement there, rather than start another email conversation. CRD can perform the reporting work behind that request.
Let Customers Choose
Offer the reports and periods they are allowed to request.
Take the Request Further
Connect that choice to the CRD job that produces their report.
Keep the Journey Familiar
Your team keeps control of the portal customers already know.
Why Choose CRD
Your Customer Experience, With CRD Behind It
Use CRD when your team wants reporting inside its own portal, with customer files, packs and recurring delivery handled behind the scenes.
SAP Crystal Server
Crystal Server’s Reporting Portal
SAP Crystal Server already provides browser-based report access, parameters, refresh and export through its platform.
Its integration components support application access. Personalized Publications require Concurrent Sessions licensing.
CRD
Your Portal. CRD’s Reporting Work.
Keep your interface, sign-in and business rules.
Map customer choices to supported reporting operations.
Request a report or a customer-specific pack.
Connect supported schedule operations to recurring delivery choices.
Display returned execution status in your customer experience.
API, packages, bursting and data-driven reporting are included in your CRD licence. No additional publishing feature licence is needed.
A Statement Request Without Another Email
For example, a customer signs in and chooses last month’s statement. Your backend selects the report for that customer, asks CRD to run it and shows the returned status while CRD delivers the file.
Choose
Select the statement and period.
Authorize
Use the customer’s permitted reporting details.
Produce
Let CRD run and deliver the statement.
Follow
Show the returned reporting status.
Turn a Customer Choice Into a Reporting Request
Your developers build the portal connection. CRD supplies the reporting operations.
Request a Report Now
Connect a customer’s request to the existing report job.
Offer Individual Files or Complete Packs
Offer a complete customer pack where needed. Packages, bursting and data-driven reporting are included at no additional cost.
Arrange Recurring Delivery
Connect recurring delivery choices to the supported schedule operations your backend implements.
Keep the Experience Yours
CRD works behind the portal your team builds and controls.
Your Customer’s Choices
Decide which reports, periods and recipients each customer can use.
Your Backend Connection
Keep API credentials on the server, behind the customer interface.
Several Customers at Once
Coordinate requests so changes to a shared reporting job do not affect another customer.
Files Inside the Portal
If customers need a download or viewer, your application provides and authorizes it. CRD performs the configured delivery.
Try the Statement Request Your Customers Ask For
Start a free 30-day trial with your existing portal and a customer report. Follow the request through CRD to the output, and see where reporting can fit into your customer journey.
Built by ChristianSteven Software
Reporting automation experience from organizations around the world.
Your Customer Portal Reporting Questions, Answered
Answers to common questions before you try CRD.
No. Your team builds the portal and backend integration. CRD’s API Service supplies reporting operations; it does not provide a portal interface or embedded viewer.
Your portal can expose on-demand requests and recurring arrangements through supported schedule operations. The available fields depend on the operation and installed CRD build.
Yes, when the package or data-driven package operation fits the request. Packages, bursting and data-driven reporting are included at no additional cost.
Your application authorizes the user and limits reports, data, parameters and recipients. An email address or parameter value alone does not isolate customer data.
Your backend needs to coordinate shared schedule changes or use separate jobs. Updates to a saved schedule can affect other requests.
It can show the returned execution status. That status does not itself confirm delivery. Any file download or viewing experience is built and authorized by your application around CRD’s configured delivery.
Show Us How Your Customers Request Reports Today
Bring the portal and a statement or pack your customers ask for. We’ll explore how CRD can handle the reporting work behind that request.