BIRT Medini nested table

Question

Hello to all the community.

At the moment I'm struggling with a feature of Medini BIRT interface.

The pourpose was to create a table for the FMEA view in AIAG VDA format.

As first try i would like to create a nested table connection, but i still not getting the values.

Medini version i'm using is 2023 R1.

Data source is Porject.medini

Data sets are:

1. "failureEntryDataSet" which has a context type: FMEA.FailureEntry and result type: FMEA.FailureEntry with a query "self"

2. "causeEntryDataSet" which has a context type: FMEA.CauseEntry and result type: FMEA.CauseEntry with a query "Sequence{self}->select(cause | cause.failureMode = failureModeId)"  it has a parameter for reference which is failureModeId which is a type FMEA.FailureEntry (referenced in query).

so the main table is binded to failureEntryDataSet yet the nested one is binded to causeEntryDataSet in which failureModeId is a javaObject with value row["@self"] but i get no result in child table.

i'm not sure what is wrong in the report. is there anybody which is more expert for an advice?

Jan Mauersberger · Answer

In addition to Marian's comment I would ask whether it is possible to use m2doc instead of BIRT. 2023 R1 is too old for m2doc but any chance to upgrade and use that technology? IMHO it is superior when it comes to nested tables, though it does not support Excel as output format.

Jan

Marian Kuban · Answer

Hi Simone,

I would first check and make sure that you pass the coorect parameter value (failureModeId) in the child DS through  the "binding" expression from failureEntryDataSet down to cruseEntryDataSet.  If you not provide it it gets the defalt value defined at DS⇒ no match → no data populated.

Also what the failureModeId supposed to represent a medini identifier or actual failure Mode Entry EMF object?

I would check the binding expression and install some debugging scripts:

* a console.log(some debug ) to see what is passed as a binding ( if anything)
* a console.log(..) into the child dataset onCreate or onFetch to see if it is even triggered

Just curious, is it intentional that you use as a first table with DS a FailureEntry ? With his configuration you will get all project's fmea Failure entry objects from any FMEA worksheet.

Marian