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; } } }

BIRT nested table data binding

medini_1063548292

Hi,

I have been trying to deal with following request.

reporintg of FMEA (fucntional) shall also include list of traced requirements related to particular function.

That basically means i need to do 2 steps:

) create table and associate it with FMEA componenent entry dataSet ( already available in standard reporting package
Obviously filtering applied (at table level) to show only components with sysml Function (contained inside [ComponentEntry].element
=>Very simple and working
) Crate nested table inside of the component entry table and setup appropriate data binding ( dataset of SafetyRequirment or bind to the custom property of parent table).
=> Tricky part

I have found very similar topic but I believe this topic was touched but not answered yet

https://medini.freshdesk.com/support/discussions/topics/1000102577

Approach with custom dataset:

context fmea ComponenentEntry

query :

-- accessing traced element's safety requirement of componenent.element using mediniGetTracedElement(SR class)
-- self.element.oclAsType(sysml::SysMLActivity).mediniGetTracedElements(safetygoals::SafetyRequirement) 

-- query only in case element is of Fucntion class (sysml::SysMLActivitiy)
if (self.element.oclIsTypeOf(sysml::SysMLActivity)) then
 self.element.oclAsType(sysml::SysMLActivity).mediniGetTracedElements(safetygoals::SafetyRequirement) 
 else 
 Set{}
 endif

outout context safetyRequirment

Reporting works but ecery componenent(fucntion)contains treaced requirments form all componenents

Here is the model i used for simple testcase

Resulting excel did not contain desired data. Seems like the self.element.mediniGetTracedElements collected SR or all components inside of the FMEA worksheet.

SO I tried to tweak a query:

- filter query result only on ccurrent component ID (as input to this dataset
if (self.element.oclIsTypeOf(sysml::SysMLActivity) and (self.mediniIdentifier =currentComponentID)) then
 self.element.oclAsType(sysml::SysMLActivity).mediniGetTracedElements(safetygoals::SafetyRequirement) 
 else 
 Set{}
 endif

However this did not work because I did not manage to pass the mediniIdentifier form component( Function) it was always <unset> => no content in the excel report

So I tried another way ( inspiried by dc_report.rptdesign). I have modified the currentComponentID->default constant <usnet> to mediniIdentifier.

Hoping taht the engine will collect this mediniIdentifier string from parent dataSet (FMEA componentEntry) column

But here is where I started to fail miserably with a lot of errors during BIRT export.

An exception occurred during processing. Please see the following message for details:
Data engine operation failed due to an unexpected exception.
A BIRT exception occurred. See next exception for more information.
Invalid javascript expression: ReferenceError: "mediniIdentifier" is not defined.

I have double checked i the datasetrow meidniIdentifier is bind to the parent table

It may be that I missing some important concept feature of BIRT datasets or data binding in general.

Any guidance would be appreciated.

Regards,

Marian

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1024169437

Hi Marian,

glad you made it, your article is reaaally long :-)

Anyway, I think the approach is valid, although I personally don't like these parameters because data sets get very specific and as you faced it, I usually forget about parameter binding.

I instead use generic data sets in first place , so one for Functions, one for FMEA entries. I then expose the list of traced elements resp. their IDs in a custom attribute.

So lets say, FMEA entry X is linked to F1 and F2, I expose the medini identifiers of F1 and F2 as "tracedFunctions" at the FMEA entry.

I then bind the nested table to the generic Functions data set and use plain filtering with an expression that the function ID must be "inside" the list of the outer FMEA entry.

That may make the report a bit slower but the work at data set a bit less painful (IMHO).

Hope that gives you another angle. I think I posted an example a while back here. If not, I could repost it.

Happy Reporting

Jan

All comments

medini_1063548292

Hi,

I was playing and investigating a bit more and was able to make this work.

the cirital point was that apparently the nested table not only needs to be bound to the dateset but also dataSet parameter Binding has to properly configured.

So in my case the undefined input parmenetr currentComponenentID had to linked through the table with parent mediniIdentifier datasetrow.

Anyways is there a better alternative way of passing data binding to nested elements other then dataSet.

I just want to simply know if by accident did not choose the most complex way

Thanks,

Marian

medini_1024169437

Hi Marian,

glad you made it, your article is reaaally long :-)

Anyway, I think the approach is valid, although I personally don't like these parameters because data sets get very specific and as you faced it, I usually forget about parameter binding.

I instead use generic data sets in first place , so one for Functions, one for FMEA entries. I then expose the list of traced elements resp. their IDs in a custom attribute.

So lets say, FMEA entry X is linked to F1 and F2, I expose the medini identifiers of F1 and F2 as "tracedFunctions" at the FMEA entry.

I then bind the nested table to the generic Functions data set and use plain filtering with an expression that the function ID must be "inside" the list of the outer FMEA entry.

That may make the report a bit slower but the work at data set a bit less painful (IMHO).

Hope that gives you another angle. I think I posted an example a while back here. If not, I could repost it.

Happy Reporting

Jan

medini_1063548292

Hi Jan,

I think I got it.

The second option to use generic dateset and exposing the parent's object list through custom property ( traced requirements) using Data Binding. So I exposed list of objects through the "@target" input parameter of Requirement data-set is indeed good and pretty simple alternative:)

So to summarize

I have added generic safetygoals:SafetyRequirement data-source with self as a query

introduced custom property in "parent" FMEA component data-set "tracedRequirements" with object(list of traced requirements) as an output
inserted nested table into the FMEA component table row and bind it to a SafetyRequirementDS
finally I have preset the @target of the preset input parameter to my custom property row["tracedRequirements"]

NEsted table Data binding to a parent table porperty

Thank you Jan again for hinting this approach.

I really appreciate it !

Regards,

Marian

medini_1024169437

Nice, thanks for sharing your experience. Please mark as answered if you find the time.

Jan