BOM quantity not matching view representation quantity

[Anonymous]

In Inventor 2016, my assembly has 6 different Views (Configurations). Each has view has components visible only to its configuration. When I made the drawings for each configuration, I added filters when creating a BOM for only that view/configuration. It works mostly and creates a BOM with only the visible components under that particular representation. However, a few components that are not visible in the assembly are still counted in the BOM. 

For example, in the master view, there is a quantity of 2 of part number ABC. Only one is visible on View 1 representation. On the BOM in the drawing for View 1 representation (with filter applied for only view 1 components), its has a quantity of 2 ABC, when it should be 1 (having only one visible). 

I can't seem to figure out why isn't this the right quantity. Thanks.

[mcgyvr]

That is normal/expected/how it works..

In newer versions (can't remember if it was in 2016 yet) but there is a check box to limit qty to visible components only..

[johnsonshiue]

Hi! I have seen this behavior before. It could be a bug or the components are not actually invisible (though geometry is invisible). Please share the files here so we can take a look. There should be a logical reason to explaining the behavior.

Many thanks!

[Anonymous]

The file is not "classified" in any way, but I do not think I can upload the files publicly. Can I email them to you?

[johnsonshiue]

Hi! Yes, please feel free send it directly to me (johnson.shiue@autodesk.com) if it is less than 50MB. For bigger file, you may want o share it on a cloud drive of your choice and let me know where to get it.

Many thanks!

[mcgyvr]

My fault.. I missed that it was only some components..

Did you split the parts list in anyway?

There was/is a bug associate with that.. 

[Anonymous]

Yes. I also filtered the list to include components 51-100. However, creating a new BOM with all the components results in the same quantity. Thanks for the help.

I'm emailing the files and will post the solution when found.

[mcgyvr · Accepted solution]

---

@Anonymous wrote:

Yes. I also filtered the list to include components 51-100. However, creating a new BOM with all the components results in the same quantity. Thanks for the help.

I'm emailing the files and will post the solution when found.

---

Thats the problem... Known bug when you split the parts list..

If you have applied all available updates then you are SOL with your older version

[johnsonshiue]

Hi Randy,

I got your email about the share on Google drive. I assume that was you. Could you describe in an email which part quantity is incorrect?

Many thanks!

[Anonymous]

We couldn't determine the cause or errors, just that it is the bug associated with 2016 Inventor BOM. My only option is to overwrite the quantity to the desired. Thanks for the help.

[johnsonshiue]

Hi! It is indeed a bug in 2016. I don't understand why the invisible occurrence is still counted when the Design View Rep Filter is on. It looks like it has been fixed in later releases with an additional option "Limit QTY to visible components".

Many thanks!
 

[bseerapathy]

 

Hi, I am using Inventor 2023. With your suggestion, The BOM is coming good according to the view rep. However, My balloon with Qty still Showing overall Qty of the Assembly instead of View rep Qty. How to make it right?

[johnsonshiue]

Hi! It looks like a bug to me or something was not set properly. Please share the files that exhibit the defective ballooning behavior. I would like to understand the behavior better.

Many thanks!

[bseerapathy]

Sample attached. I will attach the .idw separately

[bseerapathy]

.idw attached

[johnsonshiue]

Hi! Many thanks for sharing the files! I have verified the behavior on all Inventor releases. It seems like a legacy issue (a limitation). The QTY in a balloon is from the unfiltered list, while the filter is applied to the PartsList. They should be synchronized. I will work with the project team to see how we can address the behavior.

In the meantime, you may want to consider using Model States to show the design variations.

Thanks again!

[johnsonshiue]

Hi! The issue has been confirmed by the project team and reported as INVGEN-83566.

Many thanks!