Script needed for importing part number from library to BOM

Question

When we create a component in BOM and is necessary to assign a part number from library is not imported the part number in BOM.

Case of Medini 2025

Case of Medini 2023

Additionally, if is possible the description to be imported, because in case of an HW update over the development are cases when is necessary a part number update without removing the component from the BOM and the description of the component is not changing automatically for the new part number.

medini_1077483728 · Answer

Hello Jan,

Thank you for support!

The script is working!

@Smitta we need this script to work like a feature not like an external script.

Please inform us when will be available, kindly I ask to be from next release!

Have a nice day, Mircea!

medini_1024169437 · Answer

Hello Rosia,

for the first part quickly checked and could realize it with realtive low effort. Here at first an OCL validation rule (constraint) to actually find and verify parts which part number deviates from their type:

inv:
self.theType.oclIsUndefined() 
 or 
(
 self.theType.oclIsKindOf(sysml::SysMLBlock)
 and
 self.partNumber = self.theType.oclAsType(sysml::SysMLBlock).partNumber
)

In my enviroment it looks for example like this:

The smalles script to fix all deviations is this one:

finder.findByType(Metamodel.sysml.SysMLPart).butNot("theType", null).forEach(function (p) {
 p.partNumber = p.theType.partNumber;
});

I have atatche dit as script to deploy easily as well. Once executed, the OCL validation rules sould not find any deviation anymore.

Some feedback whether this is applicable in your case would be great.

medini_1024169437 · Answer

Hello Rosia,

your forum question somehow slipped, I am truely sorry for that. While the first request is pretty much clear, I am not sure about the second part.

Ah, and it seems you pasted some images but they are somehow not visible, at least to me. Could you please share them again?

Thanks you

Jan