Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.

First time visiting? Here are some places to start:
  1. Looking for a certain topic? Check out the categories filter or use Search (upper right).
  2. Need support? Ask a question to our Community Support category.
  3. Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
  4. Be respectful, on topic and if you see a problem, Flag it.

If you would like to contact our Community Manager personally, feel free to send a private message or an email.

How to make sure part property changes made from an assembly BOM stick?

CorvinCorvin Member Posts: 9 PRO

My company added a new Customer-Facing-Name property for parts, so I'm having to edit the properties for hundreds of parts. I started doing it from the BOM of a top level assembly to save time. However, I noticed after moving on to another assembly (which shares parts) that some of the parts I had already given Customer Names were not showing them. When I went back to the first assembly, they were still there, but then when I refreshed the page, they disappeared there as well. Does anyone know what might cause this or how to avoid losing work?

Tagged:

Answers

  • CorvinCorvin Member Posts: 9 PRO

    After some more testing, the problem seems to be related to versions/revisions. The changes made to the Assembly BOM from Main are only affecting whichever version/revision of the part is present in the Assembly. I must have updated some of the parts in the Assembly using the blue wheel, and it was those parts that lost their new names. This likely means I didn't successfully change any of the part names (the document doesn't own any of its own parts— all are linked from other documents). Any thoughts on how to avoid this? I know I've used this workflow to permanently change part properties in the past, so I'm not sure how I avoided this problem.

  • nick_papageorge_dayjobnick_papageorge_dayjob Member, csevp Posts: 1,027 PRO
    edited 3:16AM

    From my understanding (and my experience doing the same), changing something in the BOM table only propagates forward if the item in the table both resides in the document, AND is the "main" workspace part/subasm, not a version/revision.

    I've never found a quick way to do it. I end up going to the part studio of each part, and changing the properties there.

  • wille_jwille_j Member Posts: 8 ✭✭

    I can think of two ways you can do this;

    1. I know for a fact you can do this batched via the API, provide the assembly URL and part name mapping, and "some" python code. However, I've never done the python-API coding myself so I can sadly not help in that end.
    2. Any set of properties can be combined and written within a computed part property featureScript. I.e. if the majority of the parts would combine the part name and description into this new Customer-Facing-Name, that can be achieved in such script that write to the new Customer-Facing-Name property. This I have done loads and can help with if it's of interest.
  • CorvinCorvin Member Posts: 9 PRO

    Ah, crap. The parts are spread across about a zillion documents. Well, time to start grinding, I guess!

  • CorvinCorvin Member Posts: 9 PRO

    Unfortunately, we don't have a set in stone pattern for the new names. I'm mostly removing specific supplier names and vender PNs, that sort of thing. We just want basic descriptive names for our customer-facing drawings. I think I'm just going to have to brute force it. I'll probably still go through the top level assemblies and use "Open linked document" then "Return to Main" so at least I won't have to individually navigate to each part. It's a pain, but it's not like it would have been any easier in traditional PDM, so I'm not too bothered.

Sign In or Register to comment.