+1Hi,
I am launching a poll here to see what software IFS customers use to generate operational reporting and with what results? Customer order print, purchase order print...
We are using IFS Cloud and we would like to find options where the software is user-friendly and can cope easily with rendering depending on the data, a system that is fast while coping with projections (no metadata cash error) ...
Thanks for your help and Regards,
Anne-Sophie
+22
I would stick with Report Designer, or if you wanna build new operational reports from scratch you could go with Crystal Reports.
From what I’ve witnessed, customers modify existing layouts using Report Designer. There’s a lot of effort that R&D put into building toggic in Report Designer layout and it would be a pity to throw that out and build something on your own.
Hi,
You might want to take into consideration that Crystal Reports (also SSRS) is slated to be deprecated. While that means it will still be usable when deprecated please keep in mind that it may be completely removed in the future.
Please see -
Kind Regards,
Andreas
Apologies, just to clarify, Crystal reporting and SSRS will still work in 24R2, but it is currently set to be removed entirely in 25R1, meaning it will not work at all to use this as an option.
We use Crystal Reports for our Operational Reporting. it’s worrying that we will no longer be able to do this in future as Report Designer seems extremely limited in comparison (No Sub Reports, no grouping, no SQL fields, unable to join to other views).
My understanding is that we will not be able to achieve our current outputs in future unless Report Designer is significantly altered.
Scott
A report designer report can handle custom fields plus most of what you mention can be achieved via the business logic of any operational report. But i can understand this is a different way of working to what you are likely used to. It would seem a good idea to start planning for a transition away from Crystal reports now that you are aware it will be removed while you have time to do so. Then we will see what further improvements will come for Report Designer/Studio as well in the future.
+6A report designer report can handle custom fields plus most of what you mention can be achieved via the business logic of any operational report. But i can understand this is a different way of working to what you are likely used to. It would seem a good idea to start planning for a transition away from Crystal reports now that you are aware it will be removed while you have time to do so. Then we will see what further improvements will come for Report Designer/Studio as well in the future.
For a business like ours that has in excess of 250+ Crystal Reports this is not going to be an easy task.
The Report Designer module is still very clunky and we feel not at all user friendly.
A report designer report can handle custom fields plus most of what you mention can be achieved via the business logic of any operational report. But i can understand this is a different way of working to what you are likely used to. It would seem a good idea to start planning for a transition away from Crystal reports now that you are aware it will be removed while you have time to do so. Then we will see what further improvements will come for Report Designer/Studio as well in the future.
For a business like ours that has in excess of 250+ Crystal Reports this is not going to be an easy task.
The Report Designer module is still very clunky and we feel not at all user friendly.
Hi Daryl, that is understandable and 250+ reports will be time consuming to replace. I am not sure if you have seen the update to the deprecation notice that IFS R&D posted. You can find it here - https://community.ifs.com/ifs%2Ddeprecation%2Dlogs%2D454/ifs%2Dcloud%2D24r2%2Ddeprecation%2Dlog%2Dupdated%2D20%2Dfeb%2D2025%2D53774
As you can see mentioned there will be a ‘generic report rendering engine’ solution introduced in the future, as this will be based on XML I would guess that you could then feed the XMLs into a Crystal report server and carry on using Crystal. But I am afraid I am not aware of when this generic solution will be available.
You probably also noticed that Crystal will still work in 25R1 and not be fully removed until 25R2 giving you a bit more time to sort out your reporting requirements.
Kind Regards,
Andreas
+6A report designer report can handle custom fields plus most of what you mention can be achieved via the business logic of any operational report. But i can understand this is a different way of working to what you are likely used to. It would seem a good idea to start planning for a transition away from Crystal reports now that you are aware it will be removed while you have time to do so. Then we will see what further improvements will come for Report Designer/Studio as well in the future.
For a business like ours that has in excess of 250+ Crystal Reports this is not going to be an easy task.
The Report Designer module is still very clunky and we feel not at all user friendly.
Hi Daryl, that is understandable and 250+ reports will be time consuming to replace. I am not sure if you have seen the update to the deprecation notice that IFS R&D posted. You can find it here - https://community.ifs.com/ifs%2Ddeprecation%2Dlogs%2D454/ifs%2Dcloud%2D24r2%2Ddeprecation%2Dlog%2Dupdated%2D20%2Dfeb%2D2025%2D53774
As you can see mentioned there will be a ‘generic report rendering engine’ solution introduced in the future, as this will be based on XML I would guess that you could then feed the XMLs into a Crystal report server and carry on using Crystal. But I am afraid I am not aware of when this generic solution will be available.
You probably also noticed that Crystal will still work in 25R1 and not be fully removed until 25R2 giving you a bit more time to sort out your reporting requirements.
Kind Regards,
Andreas
We are planning to potentially hold back on 25R2 until we get our reporting sorted.
I doubt it will take us two years to get there thus keeping in the 2 year update time frame.
A report designer report can handle custom fields plus most of what you mention can be achieved via the business logic of any operational report. But i can understand this is a different way of working to what you are likely used to. It would seem a good idea to start planning for a transition away from Crystal reports now that you are aware it will be removed while you have time to do so. Then we will see what further improvements will come for Report Designer/Studio as well in the future.
For a business like ours that has in excess of 250+ Crystal Reports this is not going to be an easy task.
The Report Designer module is still very clunky and we feel not at all user friendly.
Hi Daryl, that is understandable and 250+ reports will be time consuming to replace. I am not sure if you have seen the update to the deprecation notice that IFS R&D posted. You can find it here - https://community.ifs.com/ifs%2Ddeprecation%2Dlogs%2D454/ifs%2Dcloud%2D24r2%2Ddeprecation%2Dlog%2Dupdated%2D20%2Dfeb%2D2025%2D53774
As you can see mentioned there will be a ‘generic report rendering engine’ solution introduced in the future, as this will be based on XML I would guess that you could then feed the XMLs into a Crystal report server and carry on using Crystal. But I am afraid I am not aware of when this generic solution will be available.
You probably also noticed that Crystal will still work in 25R1 and not be fully removed until 25R2 giving you a bit more time to sort out your reporting requirements.
Kind Regards,
Andreas
We are planning to potentially hold back on 25R2 until we get our reporting sorted.
I doubt it will take us two years to get there thus keeping in the 2 year update time frame.
Sounds like a sensible plan to me. Please keep an eye on what SAP plans to do with deprecating the Crystal Reports overall as well.
Best of luck!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
