Page 1 of 1

Strange Weldment Cut List Problem

Posted: Tue Oct 08, 2024 8:38 am
by JSculley
I have a multibody part file named 437514.SLDPRT. When I right click any cut list item in the feature tree and select 'Properties', in the Cut list summary, the Value/Text Expression for most of the properties are wrong. It looks like this:
image.png
If I click on any other cut list item in the list on the left and then click back on the original, it shows the correct information:
image.png
I don't use cut lists every day, so some of the inner workings are still a bit mysterious to me. Does anyone recall this as being a bug? We're still using SW2017 SP5 (going to upgrade any day now, I swear).

The only reason I even noticed this is because I was trying to manually tweak a material description of a single item in the cut list. This item is made from explosion clad plate. I wanted to add some text to the normal material description to include the cladding, without having to add a new material to the database. So, the normal material description is this:

SA 387 GR 11 CLASSS 2

and I want it to be:

SA 387 GR 11 CLASSS 2 WITH SA240-410S CLADDING

In normal custom properties of parts I do this all the time, by just appending the text in the custom properties dialog. In the cut list, any attempt to add text to the Value/Text Expression column of the MATERIAL row is instantly deleted. I can seemingly add it in the Properties Summary tab:
image.png
but it doesn't affect the cut list and the added text is gone when I go back into the Properties Summary.

Is creating yet another material in the database the only way to make this work?

Re: Strange Weldment Cut List Problem

Posted: Tue Oct 08, 2024 8:43 am
by AlexLachance
is the wrong name, the name of the part that was used as a "reference" for the save-as of the new part? If so, I've had this happen to me. Reported it in 2019, our VAR had provided a program to fix the issue and the suggestion was to have this checked:
image.png
In our case, we weren't sure if SolidWorks or CustomTools was the culprit.