Hi Oscar,

Crystal runtime engine conflicts is not the only issue you may have. I think it is worth sharing my recent experience.

Going from Sage 300 ERP v2012 to Sage 300 2022 is quit a long jump. About 2 years ago I did a similar migration (to v2019) and noticed several changes in table layouts. This affected several of the CR reports .

I opened those reports in CR Designer which raised a message informing that a table or tables used in the report had changed and gave an option to update it which also saved the report in the new CR version. So, I updated several reports following these steps. 

Cheers

Hi Oscar,

Crystal runtime engine conflicts is not the only issue you may have. I think it is worth sharing my recent experience.

Going from Sage 300 ERP v2012 to Sage 300 2022 is quit a long jump. About 2 years ago I did a similar migration (to v2019) and noticed several changes in table layouts. This affected several of the CR reports .

I opened those reports in CR Designer which raised a message informing that a table or tables used in the report had changed and gave an option to update it which also saved the report in the new CR version. So, I updated several reports following these steps. 

Cheers

Hi Tascoli,

Yes we did that and almost all reports working just a couple that for tables update we need to fix.

But in this case is more related to different CRE that use custom application and Sage 300.

Thank very much