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

Auto Counter for DC sheet

medini_1052758087

Hello Jan,

One of the customer requested IDs from Medini tool to establish traceability in DC sheet. What I could think of is a scripted column which "calculates" the auto-number based on the index of the DC sheet item and naming convention can be based on the component REF number.

For illustration purpose I have added a column in below picture. Random IDs is also Ok. Is there a script you could help with?

KR
Smitta

Find more posts tagged with

medini

medini legacy

Accepted answers

All comments

medini_1023909254

Hi Smitta,

what does the customer actually mean by "traceability"? Just having some auto-generated ID is not yet a traceability ... will he use this ID in some other place to refer to an entry in the DC sheet? Usually there is already a lot of internal traceability in medini - and using ID's for traceability is always the worst solution (except may be in a generated report).

Eckhardt

medini_1052758087

Hi Eckhardt,

Yes they wanted to use this a reference ID after generating report. They are making some customization after report generation in excel where they want to use this ID for tracking purpose.

KR
Smitta

medini_1024169437

Smitta,

I quickly took the script from this article, and adapted it a bit to generate typical "X.Y" numbers based on index, maybe that helps already. Note that I implemented it for Component Entry.

function compIdElement(e) {
	var parent = e.mediniGetContainer();
	if (!parent) {
		return null;
	}

	var myId = "" + (parent.the_owned_elements.indexOf(e) + 1);
	var parentId = compIdElement(parent);
	if (parentId) {
		return parentId + "." + myId;
	}
	return myId;
}

function compId(e) {
	return compIdElement(e.element);
}

compId(self);

Happy Scripting

Jan

medini_1023909254

But these IDs would not be fixed - if you change the structure (e.g. move a component into a different container or just change the order) the would get changed too (?)

Eckhardt

medini_1024169437

Indeed, I assumed its for one-time usage only.

Jan

medini_1052758087

Yes I understood that its for one time usage, thank you Jan for the script.

medini_1024169437

Cool. Please mark as answered later if you find the time.

Jan

medini_1052758087

Hi Jan, This could also be split w.r.t to the failure modes? Also in case is it possible if the customer wants to have a fixed one, at the moment they did not come back, just in case.

medini_1023909254

Hi Smitta,

if you have already made a property as Jan described above (e.g. named user_c_id) then you can define an additional derived property for DCFailureEntry as follows:

function compId(e) {
 var parent = self.component;
 var myId = "" + (parent.failureModes.indexOf(e) + 1);
 var parentId = parent.user_c_id
 if (parentId) {
 return 'FM-'+parentId + "." + myId;
 }
 return 'FM-'+myId;
}

compId(self);

Eckhardt

PS: Having someting fixed is probably harder ....