Inventor BoM Error

[Josh_Hudson97]

Hi,

I'm a little bit stuck with this puzzle as it has a few potential things that I can see causing it.

We're factory users (I think somewhat irrelevant for this issue, but worth mentioning). We have an assembly we publish with a phantom BoM so the correct Items are in the BoM at the Factory Layout level. Within this assembly we suppress parts using the "Component.IsActive" snippet of code. This should do a few things

1. Change the visibility of the part

2. Change the BoM structure of the part to reference

Only the first item I mention is happening in this scenario for some reason.

I can get around this in my asset prior to publishing by changing the BoM setting to hide suppressed components (As seen below)

This "Fixes" the issue with the inventor assembly environment, however not fully within my factory layout environment...

Within my Factory BoM within the model data tab is gets rid of the items would expect. However with the structured tab some of the suppressed parts remain and have a quantity of "Error".

I can't figure out if this is a code (iLogic) issue, or a Inventor BoM Issue or a Factory Design Utilities Issue. Hoping someone could shed some light on this one for me?

I'm in Inventor 2024.1.1 (btw)

[johnsonshiue]

Hi! If I recalled correctly, this could happen if some components may have incompatible unit QTY at different BOM levels. Please share the files in zip here or send it to me directly johnson.shiue@autodesk.com. I would like to understand the behavior better.

Many thanks!

[johnsonshiue · Accepted solution]

Hi Folks,

Just to provide a headsup here. Josh did send me the files. I took a look and found out it was a known issue due to suppressed common components at different subassembly levels. It was reported as INVGEN-69987. We are investigating the issue to see how we can fix it safely.

Many thanks!

[Josh_Hudson97]

Hi @johnsonshiue,

Is there any update on a fix for this yet?

[johnsonshiue]

Hi Josh,

I just checked the status of INVGEN-69987. It shows it has been resolved internally. The fix is targeting the coming 2024.3 update (April).

Many thanks!