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

BOM import with ports / post processing

medini_1059279898

Hi guys,

I have a request in the area of BOM import from excel, including ports.

Two scenarios:

1. Import type definitions, to create a new 'Element Library' of reuse components (currently possible)

define component ports as needed (new feature request)

2. Import elements, to create a new 'System/Function' model (currently possible)

map to 'Element Library' components where available (currently possible)
import new component and define component ports as needed (new feature request)

Please ask if further clarification is needed.

Many thanks,

Richie.

Find more posts tagged with

medini

medini legacy

Accepted answers

All comments

medini_1024169437

Hello Richie,

no question, the request is clear I guess. One detail: if you have use case 2 and import lets say a component A that is assigned to Type X, all ports at type X are automatcally propagated to A, no need for further ports in the BOM, right? Is that only for elements without a type definition?

Jan

medini_1059279898

Hi Jan,

Correct, case 2 only applies to elements without a type definition, i.e. a new import as such.

Some content on case 2.

I want to give users the ability to get up and running quickly with a new model, by importing via a excel, mapping to existing elements in our reuse libraries, and adding new elements/ports for the cases where there is no existing type to map to.

Best regards,

Richie.

medini_1059279898

Hi Jan,

Happy New Year!

I was discussing with Juvenal and I'm wondering if there has been any progress on this request?

Thanks,

Richie.

medini_1024169437

Hi Richie, sorry, your post was somewhat not on my radar anymore. The request is now even clearer. Just one thing I wanted to reveal (and maybe you can give it a try): The current BOM importer has already an undocumented feature to create ports! However, it only works under certain conditions which I try to explain:

- it works only for instance import

- it works only if you import into an existing part or block as container, not a model

- it works only if you have a column in your Excel which you map to "Category"

- for ports you want to create, the value must be "<Port>"

So it should look like this in Excel:

Like this in the import wizard:

LIke this in value mapping page (just press Finish and do not map the <Port> values)

and you will get:

Maybe not what you exactly want but at least something you may test to discuss further steps.

Under certain conditions this also works for type import.

Regards

Jan

medini_1059279898

Thanks Jan, I will take a look