Add iPart Data Field to BOM

[arkelec]

Not sure if what I want to do is possible.

In the attached iPart, there is a column in the data table named "Part Ref".  This is populated with a formula in Excel which concatenates two other data values, "Manufacturer" & "Part Nº".

So far, so good.

What I want to do is display the data "Part Ref" in the BOM in an assembly.

Is this possible? 

[rhasell · Accepted solution]

Hi

You need to make a custom iProperty first, in your case it will be "Part Ref"

This particular field needs to be added to the iPart table. (I will upload the files)

Then use the excel spreadsheet as per normal.

When you build the parts, the field will be available for use in the assembly BOM.

In your example I added another field called "Part_Ref" and used that throughout.

[arkelec]

Thanks so much for taking the time to reply @rhasell, just what I needed. 

I've spent a fair bit of time looking at the BOM structure & available functionality since I posted.

I think I am going to add custom fields for "Manufacturer" & "Part Nº" to each part that I design & then modify the BOM is assemblies accordingly.

Does this sound like a good idea?

[rhasell]

Hi

Yes it is an excellent idea. I have quite a few custom iProperties that are carried through myself.

There is one catch you need to be aware of.

If you have something like the following:

Stock Number = =Ø<OD> x <THICK> x <LENGTH> CHS

The User Parameters of OD, THICK and LENGTH must not be present in the default part template. (Standard.ipt)

Reason:

When you generate the parts from the iPart factory, The ipart creation will detect the presence of the User Parameters in the template, and create new values of OD_1; THICK_1; LENGTH_1

Subsequently, any calculated fields will fail, as any valid data will be place in the incorrect user parameter entries.

Hope that makes sense. (Plus it might not be applicable to you, but it is something to keep in mind for future, or if anyone else experiences this problem)

[arkelec]

Thanks again.
I'm already on the page with the naming, I've fallen foul of this sort of thing before.