AnsweredAssumed Answered

2018 virtual components do not retain custom properties

Question asked by Tom Gagnon on Mar 22, 2018
Latest reply on Mar 23, 2018 by Matt Peneguy

I have a large assembly with subassemblies that contain virtual components. This was all created in 2016 SP5. I need Custom Properties to sort and sum data in a BOM to export to Excel.

Since upgrading to 2018 (SP2), these virtual components are conditionally not retaining their custom properties. I'll elaborate.

 

What does not work: reproducible, recorded and shared to VAR

Open subassembly. Open virtual component. File Properties, Custom tab. Edit multiple Values. Click OK to close Properties. File Properties again, and what I had just entered is not present.

 

What does work: annoying workaround slightly less problematic than achieving nothing at all.

Open subassembly. Open virtual component. File Properties, Custom tab. Edit *ONE* Value. Click OK to close Properties. File Properties again to edit one value. OK to close properties. File Properties again to edit one value. OK to close properties. (Repeat as needed for eight useful properties.) Save component and close.

 

Q's:

1. Has anyone else encountered this issue?

2. Is there a real fix and not a tedious workaround?

3. Will this reoccur in other components generated in a previous release?

4. Will this reoccur in new components designed entirely in 2018?

Outcomes