We are currently trying to migrate Reports from CUBA to JMIX’s Reports add-on. Although there are no major differences, the meta class names of the entity slightly differ, eg:
CUBA - report$Report / report$Template …
JMIX - report_Report / report_Template …
This is causing an issue as we could not export our Reports from CUBA and import it into JMIX directly, and we have a big number of existing reports available. Could you please advise us on what is the best approach to this?
There is no automatical way to import CUBA report to Jmix.
Possible WAs:
Unpack exported archive and manualy change name of all report$… metaclasses to report_…. Slow in case of big amount of reports.
We have migration script (liquibase) to migrate existing reports during project migration from CUBA to Jmix 1.x (it renames metaclasses).
So you can make a “fake” migration - clone project database (do not affect your main environment) with required reports and perform migration (Migration from CUBA Platform :: Jmix Documentation). You don’t need complete migration - just make sure migration scripts are applied and reports tables & data are converted to Jmix format. After that you can export this data as SQL insert statements and apply them to database of target Jmix project.
This approach allows to process big amount of reports, but it’s more complicated and requires careful testing & dry run.
Also there can be issues if something mismatch within business-entities involved in specific report (e.g. report displays list of some entities, but this entity has different structure or metaclass name).