Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Tips when Converting Crystal 2013 to Crystal Reports for Enterprise

We are embarking on a project to convert ~450 Crystal Reports 2013 (CR2013) reports to Crystal Reports for Enterprise (CRE).  Unfortunately the project is not going smoothly due to some unexpected problems encountered during the conversion process.

We were on a 3.x system running CR2008 reports.  We migrated reports to a 4.x system and the UMT converted the reports to 2013 format....

The reports consist of the following:

1) SQL commands based on direct connections to an Oracle DB

2) Created from direct tables based on direct connections to an Oracle DB

The companies new model is:

1) SQL commands based on connections created in the IDT to an Oracle DB

2) Created from direct tables based on connections created in the IDT to an Oracle DB

The company has made the decision not to support CR2013 or direct to DB connections

The processes involve:

1) Manually opening the report in CRE and opening the report in CR2008.  We then have to copy and paste across the SQL code and remap reports.  We get a lot of errors and have to put in 'Placeholder Formulas'.

2) Manually opening the report in CRE and remapping each table in both the main and sub reports.

This is a very long and tedious process.

When testing the reports we have found a number of errors that have occurred during the conversion process:

a) The page setup defaults to a different setting  (A4 size defaulted to letter)

b) Text fields are being converted into numbers (Even if the format is changed to not include negatives or commas the actual text is still wrong thus the SQL code has to be manipulated to include 'totext()')

c) Some header formatting on tables are not set to 'can grow' and when I try to tick this setting I get a Crystal Reports error and CRE crashes!

d) Formulas have become corrupted and need to be manually fixed in the report (copy and paste from CR2008).  Also with some formulas we have to insert 'SQL_COMMAND' before the forumula thus involves quite a lot of rework.

We thought this migration would be quite straightforward but we seem to be utilising a lot of time and resources.

Please can anyone respond with their experience converting CR2013 reports to CRE and provide any tips regarding common pitfalls?

Former Member
Not what you were looking for? View more on this topic or Ask a question