Display configurations with the same name as one item

All

The BOM option labeled “Display configurations with the same name as one item” doesn’t seem to work for 2022 sp5 as I image it should. I think it did work in the past, but maybe I have that wrong. What I want is to create a BOM that itemizes the configurations of one set of components and lumps together the configurations of another. The image here shows what I don’t want. I want item one and two shown instead as 2X of one item:
image.png
I include the assembly. Is there another to try to do this?

Dwight
image.png

The “configuration name” has to be the same for that to work.

This is for different parts with the same configuration name to be listed as the same item.

What you want for your case is this instead:
image.png

If you want group the Part1 configs, without grouping the screws, one has to give the Part1 configs the same P/N.
Capture161.JPG
Capture161.JPG

Good call. I didn’t think about it also combining the hardware. Going to have to get creative.

Thanks, I find as you said that the “User Specified” option does work.

I was using the “Document Name” option (see image), which should make both part numbers match and operate the same as doing “User Specified”, but apparently it doesn’t. I think it used to work in past versions of Solidworks.

Anyway, I can live with that. Thanks very much.

Dwight
image.png

As far as I know it’s always been required to be “User Specified Name”. Help file seems to indicate such as well… Although reading all the words still makes me go crosseyed.

https://help.solidworks.com/2020/English/SolidWorks/sldworks/c_Bill_of_Materials_Multiple_Configurations.htm

Thanks, it does say that, though not clearly, especially with the last sentence saying “all”, which confuses everything.
image.png

There is a hotfix (SPR 1243187) for 2022 SP 5 available. The problem doesn’t exist in 2023 SP0.1, however it’s back in 2023 SP1 and will be fixed again in 2023 SP2 which should be available in a few weeks time.

I found that SPR as well, but when I asked my VAR for that HOTFIX they told me there is none available…

There are newer hotfixes available that also contain that fix, e.g. 1197644. Try to get that one instead.