Is it possible to make a grouped BOM from Part Lister in DX Designer? I assume it would be possible to group the BOM on for example Product Number but how do I set up Part Lister for that?
So try adjusting your Grouped part lister file to have the following:
Change Part Number to Sort Ascending, Primary Key
Change Ref Designator to Sort=None and Secondary Key.
Make sure there are no other columns set as primary or secondary keys. You may have to play around with the sorting of the other columns to get precisely what you want, I would suggest trying with no other columns sorted.
Johan - Thanks for your post. I am going to move this to a more appropriate product-related community for Design Creation in the Xpedition area. This space is for questions and suggestions about the communities in general.
If you take a look at the configuration files shipped with the product the default scheme will probably do what you want, but you may have to change the Part Number primary key to a property you wish to use. If this doesn't meet your requirements you will need to provide more details of the format you require and key propeties.
I want to make a BOM list that groups all components of the same type regardless of unique identifiers such as RefDes. This is simply to se how many of each type we have to order. I do not understand how to set this up in Part Lister? Part number is just the components name in our ordering database.
Is there a common property shared by each type, for example is there something unique you use to identify all capacitors?
Sent from my HTC
Part number is just a identifier for a certain type of component so the purchase department shall know what component to order. I simply want a BOM list that groups all components with the same Part number on one row and shows the quantity of that particular part. Each row shall contain all parts with the same Part number.Then you could just send the BOM list to a supplier.
Has this been answered or have you solved your problem in some other way? It would be nice to get the status updated.
I just wanted to report back that your suggestions worked perfect! The trick was to deselect primary/secondary key on all other properties.
Retrieving data ...