BOM Q's

BOM Q's

patmat2350
Advocate Advocate
3,111 Views
8 Replies
Message 1 of 9

BOM Q's

patmat2350
Advocate
Advocate

BOM functionality (free version)

 

1. I'm getting this message, even though there is NOTHING to refresh. Any help?

patmat2350_0-1753719962465.png

 

2. Grumble... I sure wish there was a way to fully expand the BOM, instead of clicking on every subassembly!

3. BOM can reference attributes such as material, mass... but is there any way to access color (appearance, applied either at a component level, or in an assembly onto a component)? 

I'm using F360 in place of available brick design apps for building Lego structures... they have lots of functionality but I can't stand the interface, so I prefer to design in Fusion. But one big issue is color... I prefer to have a single brick design, and apply color at an assembly level. Otherwise, I'd have to have several versions of each brick, for each available color, which has some downsides. But doing it my way, I can't list or count bricks of each color.  

 

 

0 Likes
3,112 Views
8 Replies
Replies (8)
Message 2 of 9

patmat2350
Advocate
Advocate

Regarding the update error on the displayed BOM- it is not an issue with BOMs on 2d drawings, or when I export & download the BOM...just this on-screen view. 

0 Likes
Message 3 of 9

patmat2350
Advocate
Advocate

 issue: 

> BOM on screen often, not always, shows components' default material instead of the applied material. Properties panel shows the correct (applied) material, but this is not reflected in the BOM display. May differ depending on whether the applied material was explicitly applied during component creation, vs. inherited when a new component was made (modified) from an existing design with the applied material... I haven't tested this yet.

 

 

0 Likes
Message 4 of 9

patmat2350
Advocate
Advocate

OK, this is really annoying. I need to create accurate BOMs from assemblies with hundreds of components, and "Part Number" is critical for consolidating usages through Excel pivot tables.

And yes this is for my hobby- I'm building Lego assemblies! I redesign "MOCs" for my own use and need to get parts counts and usages. But this issue will apply equally to anyone using this tool for business. 

What else?
> In the Property panel, the non-editable Part Name field is actually Part Name + version. In the exported XLSX file, Part Name does not have the version. 

> Assemblies: If a component is actually an assembly of components, it still receives the default material in Material Name. Which is unhelpful in the exported BOM.  

 

What I'm seeing: Occasional and seemingly random occurrences where the component's exported Part Number field does not match what has been entered in the Properties panel. What I see is the default value for this field, which is Part Name less the version. And sometimes if the Part Name was edited after initial creation, I see the ORIGINAL default value.   

And as mentioned, same issue for the Material name- often getting the component's default value, not the applied value that shows in the property panel.

0 Likes
Message 5 of 9

patmat2350
Advocate
Advocate

What, more? Yes, more!
In this example, Assembly Loco_27 includes 2x assembly Loco_25. The displayed BOM is correct, for example showing 1x motor 99499c01 in Loco_25:

patmat2350_0-1753894750808.png

 

 

But when I download the BOM as XLSX, motor 99499c01 is only counted once...should be total qty = 2:
 

patmat2350_1-1753894913462.png

 

So every time I use a subassembly in multiples in a higher assembly, I'm shorting my total parts count.

I'm having more reasons to abandon this tool!

0 Likes
Message 6 of 9

patmat2350
Advocate
Advocate

Annoying work-around for the miscount of subassembly parts:
Instead of using subassembly XXX 3 times, I need to save copies as XXX-1, -2 -3, and use those. 

 

Professional BOM management systems do not behave like this!

0 Likes
Message 7 of 9

john.koerner
Autodesk
Autodesk

Thanks for sharing your feedback. I have forwarded this thread to the team that is working on BOM.  

John Koerner
Message 8 of 9

andreja.schneider
Autodesk
Autodesk

Thank you for sharing your BOM experience with us. Please note that we are actively working on enhancing BOM functionalities since we are aware that current BOM capabilities are not sufficient for all our Fusion users.
These new functionalities are near completion and will be available to our Fusion users soon.
Please keep and eye on What's new Release notes for updates and new features in Fusion.

 

Best regards,

Andreja Schneider

Message 9 of 9

andreja.schneider
Autodesk
Autodesk

The described behavior seems out of place.
Can you, please, report this to our Support team for further investigation.
https://www.autodesk.com/support/contact-support?p=Fusion%20360"

 

Best regards,

Andreja Schneider