Derived Properties in reporting problem

medini_1050701002

Hi we've been having this problem with one of our report 

The context is the following : 

We have a few derived properties on failure modes :

• user_probability_class (which is computed on the failure rate of the failure mode)
• user_criticality_class (which is computed based on the severity and user_probability_class)

In the FMEA we have other derived properties on failures (~= rows in the FMEA) which simply access the user_probability_class and user_criticality_class of the represented failure modes.

Everything works great in Medini (the FMEA table correctly show everything) and in our custom FMEA report using birt when we generate it on a small FMEA.

The problems arise when we try to generate the report on big FMEAs (~= 8000 rows) :

• It takes a lot of time (which is understandable)
• Sometime it fails to compute the derived properties so they end up false 
• Sometimes it even changes the derived properties in the FMEA in Medini as well (and we have to regenerate the FMEA worksheet from the model)

We noticed that closing every other projects, and freeing the maximum amount of RAM on the computer on which the report is generated sometimes makes the computation of the derived properties correct (at ~= 50% success rate).

Our questions are the following:

• Do you have any idea what we could do to remove this issue ?
• Is it possible to "freeze" the derived properties values ? (kinda like in excel where you can pause the execution of formulas) 
• Is it possible to force Birt to not recompute every derived property ?

I'll provide further informations in the replies as needed.

Thanks,

Adrien Gérard

medini_1024169437

Gerard, this sounds weird indeed. I have no clue why it eats up so much memory or why it takes so long.

However, I have heard about problems when derived properties use other derived properties, so basically your scenario.

Could you please try the following two different experiments:

1. Open the FMEA worksheets *before* exporting the report, try to scroll a bit through the table, that  triggers the evaluation of the cells, then generate the report, any difference compared to report on closed model?
2. duplicate the code from the derived properties of the failure mode to the derived property in the FMEA, basically avoid referring to derived properties in derived properties and check the result. Is there any improvement?

Jan