Inventor 2024, Bill Of Materials

[HenrikGraversen]

Hi,

Can any explain whats goin on here in this Stock Number collum?

See the one with blue text. The Edit Expression is not active for only this sub assembly.

If i open the assembly, Stock Number looks fine.

Never seen this before. And no matter what i write in that field, it does not write to the sub assemblys Stock Number.

And it's only this one sub assembly.

Kind regards

Henrik

[YannickEnrico]

Blue + bold usually means it's a static value - And static values are not written to the respective parts and assemblies.

It's new to me that it can be set in the assembly BOM, and not just on the drawing though. Trying to figure out how to do that currently.

[YannickEnrico]

Do you happen to get anymore options than this when right clicking the field?

As you can see on the quantity, it's blue because it's set to static quantity, but I don't seem to get the same options for stock number

[HenrikGraversen]

Was my first thought to. I know it from parts list in drawing, but not in BOM. And no. There are no more options then you see there if i right click.

[YannickEnrico]

I can't find anything on it, so I would guess it's a bug.

What happens if you either:
A: Save copy as, and replace it with the copy?
B: Copy / paste all parts (they keep their contraints) into a new assembly and replace it with that?

Those are the two workarounds I can think of might work.

[johnsonshiue]

Hi Yannick and Henrik,

The blue bold text in the BOM table means it is an overridden value different than the original value. The the assembly BOM table, the change is indeed written back to the component document. Try changing the Stock Number from the file iProperty. I assume the same Stock Number should be changed back to black display.

Please feel free to share the files in zip here or send it to me directly [email protected]. I can help take a look to see if there is a bug in this case.

Many thanks!

[HenrikGraversen]

Hi Johnson

BIM does write to iprop in component.

But not if that component has other model state active, than primary.

And that was the problem.

So now I know this.

Henrik