How do I change the BOM delegation so the the Primary model state BOM to is applied other model states?

How do I change the BOM delegation so the the Primary model state BOM to is applied other model states?

dtemple25ST4
Contributor Contributor
2,748 Views
9 Replies
Message 1 of 10

How do I change the BOM delegation so the the Primary model state BOM to is applied other model states?

dtemple25ST4
Contributor
Contributor

I have an assembly drawing with multiple model states, that shows the assembly in different stages of build. Prior to model states I would have one part list for the drawing, based on the master level of detail. This made it very easy to determine if I had a part balloon created for every item in the assembly. Now, with the change from level of detail to model states, I have a part list for every model state and I don't get a "summary" of  items showing which ones have attached balloons.

 

Is there a way to change the model states so the bill of materials from the primary state is used generate the parts list for all model states?

 

The term "BOM delegation" has come up in searches, but I can't find a toggle or dialogue box that allows me to change the delegation.

0 Likes
Accepted solutions (1)
2,749 Views
9 Replies
Replies (9)
Message 2 of 10

Gabriel_Watson
Mentor
Mentor

Is there a way to change the model states so the bill of materials from the primary state is used generate the parts list for all model states?


For that, yes. When placing your parts list you can choose which Model State to acquire the BOM from:
Capture205.JPG

As for the real problem you are facing, I could not be sure from your post if you need the BALLOONS to follow another numbering order (skipping suppressed items) depending on which Model State a view is made from, or if you would like something similar to this below, where iLogic can be used to find which balloons were not applied:
https://forums.autodesk.com/t5/inventor-ilogic-api-vba-forum/using-ilogic-to-look-for-missing-balloo...

Message 3 of 10

dtemple25ST4
Contributor
Contributor

Thank you for the reply, but I think I'm looking for something else.  I believe Inventor uses the term 'BOM delegation' to refer to what I am calling 'linked' below. The information I've found is not very helpful so far.  This comes from an ongoing process of getting used to the differences between the old Level of Detail versus the new Model States.

 

I have an assembly with 3 models states: Master, model state 1, and model state 2. 

1) I created a drawing with 3 sheets, each representing a view one of the model states.

2) I generate a parts list on sheet 1 which has a view of the master model state.

3) I attempt to add part balloons to all parts on sheets 1 to 3. All of these parts are listed on the parts list on sheet 1.

4) The BOM of the master is somehow linked to model state 1 but not model state 2

     a) All of the balloons added to the view that was based on model state 1 show up on the parts list generated from the master model state on sheet 1. (I'm referring to the balloon icons that show up in the far left column of the parts list).

5) When I tried to add balloons to the view based on model state 2, it prompted me to generate a new parts list from the BOM for model state 2 and I could not select the master model state; only model state 2.

 

I'd like to know how (if it is possible) to change the model so that the master BOM is linked to both of the model states.

 

 

0 Likes
Message 4 of 10

johnsonshiue
Community Manager
Community Manager

Hi! The answer is no. The BOM delegation only applies to migrated assemblies with legacy LOD. It is because in the past, there is only one BOM. All LODs share the same BOM. Without delegation, these migrated assemblies will have different BOMs on open, which can affect drawings.

The behavior you described sound like a bug to me. Have you installed 2022.2 update? Could you share an example that exhibits the behavior?

Many thanks!



Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer
Message 5 of 10

dtemple25ST4
Contributor
Contributor

Thank You for your reply. I was afraid that was going to be the answer. It may be that I have to change my process for assembly drawings. Early on I started using Level of Details to show build steps for assemblies. I can't remember why now but using LODs had a certain advantage vs. using Views.

 

Anyway, one of the features I utilize frequently is generating the part list for the assembly and then opening it to track whether I have added part balloons on the drawing to all parts on the list. As you stated with different LODs they still all shared the same parts list.

 

Now that the Model States have replaced the LODs, each model state appears to have it's own BOM, so the generated part lists are independent and I cannot look at one list to determine if I added balloons to all the parts on the list.

 

My guess is that now I will have to create the assembly build steps using Views instead of Model States to use a common part list in this way.

 

If that is not true and I am experiencing some type of bug, I can send you a drawing and model that exhibits this behavior.

0 Likes
Message 6 of 10

mshirleyBPVSC
Observer
Observer

I am wondering if this issue was ever figured out for you or did you end up using views?

0 Likes
Message 7 of 10

johnsonshiue
Community Manager
Community Manager

Hi Folks,

 

Recently we just found a workflow which does allow you to create Model States but the BOM still points to Primary only. Essentially, the Model State BOM behaves like migrated LOD BOM.

If this is what you want, here is the workflow. You simply need to open an iam template in 2021 and create the empty custom LODs as you wish. Save the template file. Then use this template file in 2022 or later to create new assembly. These Model States (migrated LODs) will delegate their BOMs to the Primary BOM. It behave as if the Model States were migrated from 2021 or earlier LODs.

Use at your own risks since this isn't a designed workflow. We are not blocking it right now. But, we don't know if there could be bad consequences down the road. In theory, this is not much different than migrating LODs.

Many thanks!



Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer
0 Likes
Message 8 of 10

tomasz.sztejka
Advocate
Advocate
Maybe because selected view representations of sub-assemblies are turning back to master when you toggle sub-assembly visibility? For me it was a blocker and I also ended up testing the LoD path.
0 Likes
Message 9 of 10

GustavoGonzattoSchmitt
Participant
Participant

Is this a feature alredy on newer versions of Inventor?
That's exactly what I need!

0 Likes
Message 10 of 10

johnsonshiue
Community Manager
Community Manager
Accepted solution

Hi! Yes, it is available in 2026.

Many thanks!



Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer
0 Likes