IFS Cloud reporting · Crystal Reports deprecation
Crystal Reports integration in IFS Cloud: pick the replacement per report type
The Crystal Reports integration in IFS Cloud is deprecated and IFS plans to remove it in 26R2. Each kind of Crystal report has a different replacement, so the first job is to sort your reports by type, not to start rebuilding.
IFS has deprecated the Crystal Reports integration in IFS Cloud and, according to an IFS employee in the IFS Community, plans to remove it in 26R2. Operational report layouts move to IFS Report Studio, ad-hoc Crystal Quick Reports move to Lobbies or Power BI, and a customer who wants to keep Crystal after the removal needs a custom integration.
Key takeaways
- The plan changed twice. The first notice planned removal with 25R1. The notice revised on 20 February 2025 staged it: deprecated in 24R2, no longer sold in 25R1, current integration unavailable in 25R2.
- Support was then reinstated in 25R2 service update 3, stays in 26R1 and is planned for removal in 26R2, according to IFS employee posts in the IFS Community.
- Operational report layouts (order confirmations, purchase orders, invoices) go to IFS Report Studio, a web-based designer that stores layouts as .rep files.
- Ad-hoc Crystal Quick Reports go to Lobbies or Power BI, not to Report Studio.
- Keeping Crystal after the removal is possible only through a custom integration, for example through the External Reports Gateway, and that integration becomes your code to maintain.
1.What does the Crystal Reports integration in IFS Cloud cover?
The Crystal Reports integration in IFS Cloud renders report layouts designed in Crystal against data that IFS Cloud prepares. In practice it touches three kinds of objects, and each one leaves the integration by a different route:
- Operational reports with a Crystal layout: business documents users print, e-mail or archive, such as purchase orders, delivery notes and invoices.
- Crystal Quick Reports: ad-hoc listings and analyses that users run on demand.
- The rendering services: the Crystal web services in the landscape that turn a layout and its data into a document.
This article sorts those objects by replacement. The release-by-release status is kept short in Crystal Reports in IFS Cloud, and the full rebuild method (inventory, triage, rebuild patterns, testing) is in IFS Cloud Crystal Reports: release status and migration.
2.How did the deprecation plan change?
The Crystal deprecation plan in IFS Cloud has had three versions, and a project plan built on the first or second version is now wrong. All three are visible in the public IFS Community thread Removal of Crystal Reports in 25R1.
| Version of the plan | What it said | Where it was published |
|---|---|---|
| First notice | The integration was planned to be removed entirely with 25R1. | Deprecation log entry quoted in the first post of the thread, January 2025 |
| Revised notice (20 February 2025) | 24R2: deprecated, still available, fully functional and supported. 25R1: no longer sold, still supported for 24 months for upgrading customers with existing Crystal licences. 25R2: current integration no longer available. | IFS Cloud 24R2 deprecation log, revised 20 February 2025, posted by the IFS Community account |
| Current plan (from February 2026) | Support reinstated in 25R2 service update 3, scheduled for 19 February 2026. It remains in 26R1 and is planned for removal in 26R2. | Posts by an IFS employee of 5 February and 27 May 2026 |
The 27 May 2026 post states that the legacy integration is still up for removal in 26R2 and that most standard operational reports have Report Studio based layouts in the 26R1 general availability release. These are employee posts in a community thread, not release notes, so the release documentation for your own version takes precedence. How service updates differ from release updates, which matters for the 25R2 reinstatement, is explained in service update vs release update.
3.What replaces each kind of Crystal report?
The replacement for a Crystal report in IFS Cloud depends on what the report does, and the revised deprecation notice names a different tool for operational layouts than for ad-hoc reporting.
| Crystal object | Replacement named by IFS | What it means for the project |
|---|---|---|
| Operational report layout | IFS Report Studio | A layout rebuild per document. Check first whether your release ships a standard Report Studio layout for the same report. |
| Crystal Quick Report (ad-hoc) | Lobbies and lobby elements, or Power BI using BI Analysis Models | A redesign, not a copy. A lobby element or a Power BI view answers the same question in a different form. |
| Crystal kept after removal | Custom integration, for example through the External Reports Gateway | Your own integration to build, test at every update and support, with no standard IFS layer underneath. |
IFS documentation describes Report Studio as a web-based tool used to design layouts for operational reports, based on JSON data sources. Users need the FND_DESIGNER_REPORT permission set to launch it, and layouts are stored as .rep files. See the IFS Report Studio page in the IFS Cloud technical documentation. For ad-hoc reporting, the build steps for lobbies are covered in lobbies and custom dashboards in IFS Cloud.
4.Which decisions should be taken before the rebuild starts?
Four decisions shape the Crystal exit, and each is cheaper to take before the first layout is redrawn.
- Sort every Crystal report into one of the three types. An operational document and a quick report with the same name are different work items with different tools.
- Decide rebuild, redesign or retire per report. A report nobody has run in a year is a retirement candidate. Customer-facing and legally required documents come first.
- Decide whether any report justifies a custom Crystal integration. The answer is usually no for standard business documents, because the custom route turns one migration into a permanent maintenance item.
- Put the Crystal exit into the upgrade plan with a date. The target release for the upgrade decides the deadline: a project heading for 26R2 must finish the rebuild before that upgrade.
The fourth decision belongs in the same inventory as extensions and modifications before each release, described in IFS Cloud upgrade readiness. Keeping rebuilt layouts inside the standard layout tools also keeps them out of the tailoring levels that need retesting at every update, explained in IFS Cloud tailoring levels.
5.Where do Crystal exit projects go wrong?
Crystal exit projects go wrong when the plan treats every report as a one-to-one conversion into Report Studio.
- Planning on an old version of the plan: a team that read only the February 2025 notice may have rushed a rebuild for 25R2, and a team that read only the reinstatement may believe Crystal stays.
- Quick reports sent to Report Studio: the revised notice points ad-hoc reporting to Lobbies and Power BI, so rebuilding a quick report as an operational layout spends effort on the wrong tool.
- Counting on automatic conversion: treat any converted layout as a starting point and compare its printed output with the original before sign-off.
- No owner for the rendering services: The Crystal web services and any scheduled jobs that distribute Crystal output are infrastructure. Somebody has to switch them off and confirm that nothing still calls them.
If you want this sorted for your own report catalogue, the reporting and customisation work sits in my services for IFS Cloud.
6.Frequently asked questions
Is the Crystal Reports integration still supported in IFS Cloud?
The Crystal Reports integration in IFS Cloud is deprecated but still supported in 24R2, in 25R1 for upgrading customers with existing licences, in 25R2 from service update 3 and in 26R1. An IFS employee stated in the IFS Community in May 2026 that the integration is still planned for removal in 26R2.
What replaces Crystal operational reports in IFS Cloud?
IFS Report Studio replaces Crystal for operational report layouts in IFS Cloud, such as purchase orders, delivery notes and invoices. Report Studio is a web-based layout designer that uses JSON data sources, stores layouts as .rep files and requires the FND_DESIGNER_REPORT permission set.
What replaces Crystal Quick Reports in IFS Cloud?
The IFS Cloud deprecation notice revised on 20 February 2025 points ad-hoc Crystal Quick Reports to Lobbies and lobby elements, or to Power BI using BI Analysis Models. Report Studio is named for operational report layouts, not for ad-hoc reporting.
Can we keep using Crystal Reports with IFS Cloud after 26R2?
Keeping Crystal Reports with IFS Cloud after the removal planned for 26R2 requires a custom integration, for example through the External Reports Gateway, as an IFS employee wrote in the IFS Community in May 2026. That integration is customer-owned code that has to be tested at every IFS Cloud update.
Why did the Crystal Reports dates in IFS Cloud change?
The Crystal Reports dates in IFS Cloud changed because IFS revised the deprecation notice in February 2025 and then reinstated support in 25R2 service update 3. The first notice planned removal with 25R1, the revised notice made the integration unavailable in 25R2, and the current plan keeps it until removal in 26R2.
7.About the author
Dariusz Myśliwiec: 18 years hands-on with IFS (Apps 7.5 to 10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Independent practice based in Kraków, delivered remotely across Europe and globally. You talk to the consultant who does the work, not a sales layer.
Selected clients from my IFS work: Fugro · LGC · BVI Medical · Betafence (PRÆSIDIAD) · Barlinek · NGK Ceramics · Newag · Oleofarm.
IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
How many of your reports still render through Crystal?
Send me the list, or the question you cannot answer yet. In a technical call we sort the reports into rebuild, redesign and retire, and set the date the Crystal exit has to meet in your upgrade plan.
Book a technical call about your Crystal reports See services for IFS Cloud
