table together carpenters

[TECNOMECH]

Good morning, guys.
I wanted your opinion on how you proceed in such cases?
I have to. make a table of a particular welded. the table is handled with three sheets:
- mechanical processing
- carpentry together
- cuts
I find that in the detail of the individual cuts I must indicate by hand the position because I can't tie it to the file together.
each cut will be called with the location I indicated in the list parts.
the problem arises when I change the order.
the position indicated in the individual cuts must be manually updated.
Is there a way to tie them?

 

[Matteo Cappelli dis.CAD]

I would do this personally:
in the assembly file I create a visual representation where only the components you want to see in the cutting list are visible
then in the sheet where you only show the cutting components, I would make a separate using the filter and then displaying only the visual representation previously stored
attention (as from autodesk advice) to quantities
I hope I have understood the problem and I have explained
Hi.

 

[TECNOMECH]

Hello, matteo.
Thank you for the answer. I wanted to find an alternative to the method indicated by you because if you add a new part in the set I have to go over all the configurations of the views and hide it.

 

[stefanobruno]

distinct " only parts " compiled in the set, I create a custom column that I call pos_bom.
Fill out the field " element " with the number of position that will take in the table.
copy and paste the values of " element " in pos_bom.
I make the table with the ball, clearly choosing the distinct " only parts " for the selected view.
I make the table of the semi-finished and I can put a director, who points on the piece, containing the field "custom properties - model - pos_bom ".
this director I can copy it from the table of one piece to another and will always assume the correct value, as long as they keep the fields " element " and " pos_bom " synchronized, which is definitely simple by retracing from the distinction on the set.
also the name of the view can be managed in the same way, but you have to do so by changing the default name of the view itself, always with "custom properties - model - pos_bom ".
the explanation of the procedure is a bit twisted but everything works well, of course it is not the automatism you wanted but it is better to have to fill in manina all with the risk of wrong.
probably with two lines of code you could do it very well, if one was capable.

 

[TECNOMECH]

excellent solution.
Big stefano.

 

[stefanobruno]

of the series: if the program already does all of him, what am I enjoying?