Minor BIRT reporting issue in 2020R1

Question

Hi Jan,

In 2019 R3, when I added any new .rptdesign
files into the corresponding directory, the report option will automatically
appear in the Report menu:

However,
when I tried the same thing in 2020R1, there is no “additional” menu appear; And
when I tried to generate report via “Generate Custom Report…”, the following
error message was prompted:

Any idea what might I missed?

FYI, I have successfully installed BIRT add-on in 2020R1 and was able to open .rptdesign files in the Report Design perspective.

Thanks!

Chi-Seng

medini_1038653923 · Answer

Thanks for the clarification!

Reporting not happy yet~

Chi-Seng Lee

medini_1024169437 · Answer

Whether a report design can be safety taken as is from one version to another depends on the changes we have done to our metamode

and how much "glue" code we introduced to keep the impact to scripting and reporting to a minimum.

With 2020 R1 we for example forced users to name their customer profile properties with a "user_" prefix

but we inserted legacy code so that access to "user_foo" or "foo" is both supported.

For FMEA I think the changes we have done to the cause/effect chain makes FMEA reports from 10.x

incompatible to 20.1

So yes, there is always a chance that a report needs adaptation as well.

For standard reports we actually do that of course, but not for custom.

Happy Reporting

Jan

medini_1038653923 · Answer

Hi Jan,

I've found the cause of the above issues!

Issue#1: Customized report design does not show up in drop down menu

The reason is simply because the container of the report design files should be "...\config\reports", instead I put it in ...\config\report, without the "s" in "report" folder.

Issue#2: Error in report generation

The sample report design "fmea_report.rptdesign" was copied directly from the Medini directory "...\plugins\de.ikv.analyze.reporting_1.0.1.201910041058" of 2019R3 version. This report generation works fine in 2019R3.

However, if this exact file was copied directly into 2020R1 project workspace, the above error would be invoked.

If I copied the corresponding file from ...\plugins\de.ikv.analyze.reporting_1.0.1.201912181408 of 2020R1 version, then there is no error.

I tested the following:

1. In 2019R3, copy  "fmea_report.rptdesign" from "...\plugins\de.ikv.analyze.reporting_1.0.1.201910041058" and put in ESL\config\reports.

2. Export the ESL project into mprx file

3. In 2020R1, import and migrate the above mprx file

4. Execute report generation for "fmea_report" (by either way), the above error will be invoked.

The mprx file is attached in this post for your reference!

Of course, there's a good chance the error is specific to the fmea_report.rptdesign file, but doesn't this also imply that for some report design files, error might be introduced when they are migrated to newer versions?

Chi-Seng