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 - How to get related Safety Goals or Requirements as dataset

medini_1053080245

I have tried to find the answer into the existing topic but it remains unclear for me how to do it (step by step).

I would like to get all the related upper requirements (here it is Safety Goals but it could be FSR, TSR... at lower level) for a given requirement table as a dataSet.

I have a dataSet-A to list all the requirements and I can see the column "related Safety Goals" but how to proceed then to be able to have a dynamic Dataset-B that will contain all the related Safety Goals (and their related fields) for a given Safety Requirement ?

Basically I would need to build a report where every subchapter

describes a Safety Requirement (description, name, identifier...)
list all the related Safety Goals (identifier, name...)

This is an example of what I need but my request is more general to understand how it works to join dataset, and then avoid to create multiple topic tickets ;-)

Thank you in advance

Find more posts tagged with

medini

medini legacy

Accepted answers

All comments

medini_1053080245

I am now a step forward from this post ;-)

I have found from existing template in this forum, the following code to be added to a computed column of the SafetyRequirement DataSet:

It works to get all the SG's name related to the requirements (results are ok in preview result).

It works also when I put this dataSet into a table.

But I have the following error when I generate a report with this table embedded in a master table as a sub table:

medini_1053080245

If I do the following action, seen in another ticket, the previous issue is solved...but the report generation take lot of times compared to previously...

"Need cache for data-engine" set to False in the DataSet option.

medini_1024169437

Hi Romain, sorry for not having answered earlier.

Yes, you stumbled over one of our biggest pains a report designers. The OCL data source does not work well with caching and custom columns, but disabling the cache will make the report slow because BIRT is creating the data sot many many times.

I have no ideal solution, one is to really have the computation for your custom columns only once to allow caching, so the first time you can navigate via row["@self"].getObject().XXX() but later this object is not anymore available as such due to the cache. You somehow need to make sure that you only navigate in the first call.

The other option is to move this kind scripting into the medini side as derived properties, uncheck them to hide them in the UI. Then access them calculate from the BIRT data source so you do not have to navigate that much.

Jan

medini_1053080245

Ok thanks. It works so for now I am happy ;-)

medini_1024169437

Cool!

Jan