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

Export DC sheet with hierarchical structure

medini_1035403171

Dear all,

Exporting a DC sheet leads to a file without any hierarchical information (table export as well as per "generate report"). All entries are simply listed beneath each other no matter on which hierarchical level they are. This makes the resulting document quite unreadable. Is there a method to include this hierarchical structure in the exported file (preferable Excel but also pdf)? Either with an indent or in next column.

Thanks,

Johannes

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1024169437

Sure Johannes, it does. Meanwhile, you could use a simple scripted property.

Note that metamodel wise the hierarchy is in the sysml, not directly in the DC.

Here an very simple example of a hack that returns the name with a prefix depending on its level:

function sysLevel(e) {
	if (!e.mediniGetContainer()) {
		return "";
	}

	return " " + sysLevel(e.mediniGetContainer());
}

function dcLevel(entry) {
	console.log("{0} {1}", sysLevel(entry.element), entry.element.name);
}

finder.findByType(Metamodel.dc.DCComponentEntry).forEach(dcLevel);

If you put that into a derived property of a DC Component Entry like this maybe:

...
dcLevel(self);

you may end up with:

and ultimately:

Happy Reporting

Jan

All comments

medini_1024169437

Hi Johannes,

next column is most likely difficult. I see some options:

develop a custom column that shows the component name but with indent and replaces the original column (without indent)
really change the report design so that is adds indent based on the level

The first does not require to edit the report design but will work only for the real table export, not the other DC reports.

What do you think?

Jan

medini_1035403171

Hi Jan,

the custom column sound good because it seems more versatile. Can you help me on that one?

However, it also might make sense to generally change the DC sheet report design accordingly. Having no hierarchy in the output file makes no sense for me because the report becomes very difficult to read. Or is there any reason I missed?

Thanks for you support,

Johannes

medini_1024169437

Sure Johannes, it does. Meanwhile, you could use a simple scripted property.

Note that metamodel wise the hierarchy is in the sysml, not directly in the DC.

Here an very simple example of a hack that returns the name with a prefix depending on its level:

function sysLevel(e) {
	if (!e.mediniGetContainer()) {
		return "";
	}

	return " " + sysLevel(e.mediniGetContainer());
}

function dcLevel(entry) {
	console.log("{0} {1}", sysLevel(entry.element), entry.element.name);
}

finder.findByType(Metamodel.dc.DCComponentEntry).forEach(dcLevel);

If you put that into a derived property of a DC Component Entry like this maybe:

...
dcLevel(self);

you may end up with:

and ultimately:

Happy Reporting

Jan

medini_1035403171

Great, that looks good. Can you help me where I need to put what now..?

medini_1024169437

Johannes, you need to profile the "DC Component Entry".

For your convenience, I attached my sample project and stripped it down to the bare minimum.

The project is made with 2020 R1.

Happy Scripting

Jan

medini_1035403171

Okay, got it. Thank you. I adjusted the code from above. This is how the output looked good for me. Maybe someone else can benefit from this:

function sysLevel(e) {
	if (!e.mediniGetContainer()) {
		return "";
	}

	return " " + sysLevel(e.mediniGetContainer());
}

function dcLevel(entry) {
	return sysLevel(entry.element) + 
		(entry.element.partNumber != "" ? "[" + entry.element.partNumber + "] " : "") + 
		entry.element.name + 
		(entry.element.alias != "" ? " : " + entry.element.alias : "");
}

dcLevel(self);

medini_1055920722

Can someone help me out as in where to put this piece of code?

medini_1035403171

Sure. You go to Project Settings / Profiling / Diagnostic Coverage / DC Component Entry and create a new derived property. Then you enter the code from above.