Sorting repeat region based on model tree

[amatsu42]

Good morning everyone,

I tried searching for a few hours on how to solve this problem to no avail, so here goes.

I created a BOM in my 2D drawing by creating a repeat region listing, from left to right, quantity; index; mbr name; user defined description. When I first populate this table it's perfect--the BOM is sorted identically to my model tree.

The problem arises when I remove duplicate entries in an attempt to accurately display quantity. This forces the organization of the table to alphabetical based on mbr name and I cannot for the life of me figure out how to go back to model tree organization. I tested out using rpt.level but those get deleted as soon as I remove duplicate as well.

Attempted solution:
For our purposes I cannot add random columns to sort by. I added parameters called index (type integer) and forced the repeat sort by to be based on that. This worked, but if I need to use these parts in another assembly suddenly I have overlapping parameters. Moreover, I can only sort by this parameter if it is in the table.

Any help is appreciated!

--I use wildfire 5.0 Creo

 

[mjcole]

There are options for the table to show or hide duplicates which will allow you to avoid the issue altogether.

You can add a column for Feature Number of the components to sort by which will automatically be in integer order.

"It's not the size of the Forum that matters, It's the Quality of the Posts"

Michael Cole
Boston, MA
CSWP, CSWI, CSWTS
Follow me on !w¡#$%
@ TrajPar - @ mcSldWrx2008
= ProE = SolidWorks

 

[geesamand]

As you noted, rpt.index follows the component ID's, which are assigned in order of addition to the assembly. As soon as anyone does modifications to the assembly, this loses agreement with the model tree order.

You need to force the order using the Fix Index command for each item.

David

 

[mjcole]

Good tip David,

Thinking about the simplest solution.

Wouldn't the easiest method to get the Model Tree order be to just Reapply the BOM Table. I guess it also depends on the size of your BOM in terms of total unique components. Davids method of using Fix index may work better but may get too complicated as the number of rows increases.

Would it be possible to show a portion of your Table in a before and after method so we can see the specifics of what's happening as you mentioned using rpt.level and other methods. You can blank or scramble any Confidential information in your table.

By Reapplying or Creating a new BOM you can get the original order back again to match your tree. Before Deleting and Re applying Table you can copy the contents to a Basic Table as a backup.

"It's not the size of the Forum that matters, It's the Quality of the Posts"

Michael Cole
Boston, MA
CSWP, CSWI, CSWTS
Follow me on !w¡#$%
@ TrajPar - @ mcSldWrx2008
= ProE = SolidWorks

 

[geesamand]

I have not found that to work when I tried it in the past. The component id's are permanently fixed to each component and they ascend in the order they are added to the assembly, not in ascending order according to the model tree. If you move around the components in the model tree the component id's (and sort order) stay the same. If you re-do the table I've found you always get the same thing. Feel free to try it, it takes only a few seconds.

Perhaps your bom table file is based on a different parameter to create the index?

David

 

[amatsu42]

Thank you all for the responses! Apparently the email notifications were getting filtered.

I can try posting the table later, but the problem I have is that when the table first populates it does match the layout tree. The leftmost table entry (what I'm told it sorts by) is Item # (controlled by index), then left to right is part number, description, and quantity.

The only time that the BOM jumps from the order of my model tree to alphabetical (by part number) is when I tell the table to eliminate duplicate entries (thus populating the quantity column).

If this doesn't make sense I'll include some screen shots to help explain.