Filter Worksheet to Excel or M2Doc

medini_1071979742

Hello,

I need a way to filter multiple DC worksheets by SG1 and need the "name" (SysMLElement) of the affected rows.

In final, it should be in Excel, but M2Doc is also fine.
By filtering a worksheet itself, SG11, SG12..SG1N is also displayed. How can I self this problem?

Regards Lisa

medini_1059007410

Hi Lisa,

to see the list of elements, which in a DC sheet are related to a specific safety goal (e.g. "SG-001"), then you can use the below in an M2Doc report:
{ m:myDC1.components->select(c|c.safetyRelatedFor.identifier->includes('SG-001') or c.safetyRelatedFor->isEmpty()).element.name->sep('\n') }

You mentioned that you will be doing this for multiple DC sheets - does that mean that you want to compare the resulting lists?

For this, you wouldn't need to export them and then do manual comparisons, but you can also use AQL for this, e.g. like this:

{ m:let filteredComponents1 = myDC1.components->select(c|c.safetyRelatedFor.identifier->includes('SG-001') or c.safetyRelatedFor->isEmpty()) }

This creates the above list within a let variable for further use. Same for second DC sheet:

{ m:let filteredComponents2 = myDC2.components->select(c|c.safetyRelatedFor.identifier->includes('SG-001') or c.safetyRelatedFor->isEmpty()) }

Components, which are related to SG-001 in DC1, but not in DC2 (note that we are comparing the elements with .element themselves, as the components are different per DC sheets):

{ m: filteredComponents1->select(c|not filteredComponents2.element->includes(c.element)).element.name->sep(', ') }

Similar - components, which are related to SG-001 in DC2, but not in DC1:

{ m: filteredComponents2->select(c|not filteredComponents1.element->includes(c.element)).element.name->sep(', ') }

And don't forget to close the let statements (that's how far they are valid):

{ m:endlet }  { m:endlet }

Does that fit to your use case?

Happy reporting/scripting,

Nils

P.S.: These operations are of course also possible in OCL properties (I guess with a bit more oclAsType than here in AQL). And AQL itself will be available in 2025 R1 as a derived property language (beta feature, to be activated in Preferences) :-)