How do you currently address this problem, without creating a new configuration?
Imagine you have an assembly with several display states. Each display state has various components hidden. What is visible in each display state represents a different variation of the product.
There are major benefits for using display states instead of configurations for that, but I suggest we do not debate them here.
When creating a drawing view, representing a certain display state, the user would like to get a BOM containing only the visible components.
One way to achieve that is to autoballoon the drawing view, reveal the ballooning status in the BOM and use that column for manually hiding rows that have no balloons attached.
Is there a better way?
Note that Exclude from BOM or envelops would not work in this scenario, since such settings would apply to all display states.
I suggest that we need an extra filter for the BOM based in the hide/show attribute of a component. If I could just create a column where I can see one of two values: Hidden or Shown, so I could sort by that column and then manually hide the rows with the Hidden value, that would be a huge step in the right direction.
Matthew Lorono, what do you think? Anyone else?