nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

FMEA Report Generating Error

medini_1044914794

Hello, this is Daehui Jeong in HancomMDS which is located in Korea.

Recently, we were provied FMEA generating birt script to customer.

And some error was occurred on the customer side as below.

The problem was occured by ChapterIndex.

But ChapterIndex was defined in birt, and this script already was tested before providing.

Could you give me the answer what occurred this error?

Find more posts tagged with

medini

medini legacy

Accepted answers

All comments

medini_1024169437

Hi Daehui Jeong,

just to clarify, this is a custom report that you have created and provided to the user (customer)?

If yes, is it based on our default FMEA report? What have you changed there?

I assume you and the customer have the same version, right? Which one is it?

Background: I need to understand whether this is a support request or an issue with a BIRT design you have created.

Regards Jan

medini_1044914794

Hi Jan,

It's right.

Based on default FMEA report, I was add one table more about HAZOP and some FMEA column.

And both of side are used R2.

Best Regards,

- Daehui

medini_1024169437

Ok, got it. So what is "Chapter Index" in your case, have you created that?

Is it a data set or a script function?

Need some more info on that one. ... I think its not in the original design.

Jan

medini_1044914794

ChapterIndex is not made by me.

It is defined in javascript_lib.js.

This js file was declared analyze_data_set_library.rptlibrary, and default FMEA report used it as below.

And those of three files are located in same directory.

- Daehui

medini_1024169437

Thanks Daehui,

yes, the JS object was introduced with 19.0 exactly supporting the FMEA report for measure groups (cell spanning). So my first impression would be that the file is different at customer side. Have you shipped the report so the customer can overwrite the standard report (so just the design file) or have you shipped it together with the library *and* the script file together so the customer is using "Generate Custom Report"?

Btw. the image from the first article got broken, could you please post it again?

I think you posted it as link but better attach it as inline image.

Thanks

Jan

medini_1044914794

Thanks Jan,

We didn't provide only birt script.

Make a report directory to the sample medini project, and copied birt script with js file and rptlibrary file.

After then we were provide medini project file that exported to the customer with guiding about "Generate Custom Report".

As below figure is firtst article's one.

Thanks,

- Daehui

medini_1024169437

Ah, so you put the report + JS file + libraries *into* a medini project but though use "Custom Report", actually selecting a file on the fiel system? Or did you explain to the customer to use the Report Context menu entry?

Jan

medini_1044914794

Yes right, the report generated through "Custom Report".

We guided to the customer like this.

- Daehui

medini_1024169437

Thanks Daehui,

but you still have stuff inside a medini project is this medini project just to deliver the report to the customer or is it the final medini project with the actual safety data that "feed" the report?

The difference is that in the later case the user may use the context menu and generate the report directly, not using "Custom Report".

Did you tell the customer to navigate from the Custom Report wizard to the file system of *your* medini project with the rpddesign, or did you tell him to merge things over to his project?

Jan