Summary
In assembly mode, custom critical values don't carry their names over effectively across components. The custom field shows up with a generic placeholder name (e.g. "Custom Column3") instead of the name it was given.
Environment
- App: Eva (B&J org), Assembly mode
- Packet:
FAS-01-1510-0034-A B&J.pdf
- Component selected:
03-1510-0344 (Drawing 66473SCS, Century Spring)
Observed
- The Critical Values panel shows a custom field labeled
Custom Column3 (highlighted red) with value 2534, rather than the intended custom name.
- The custom critical value name does not transfer/persist correctly per-component in assembly mode.
Expected: Custom critical value names defined in assembly mode transfer over and display consistently (per component) rather than reverting to a generic "Custom ColumnN" label.
Screenshot attached below.
Summary
In assembly mode, custom critical values don't carry their names over effectively across components. The custom field shows up with a generic placeholder name (e.g. "Custom Column3") instead of the name it was given.
Environment
FAS-01-1510-0034-A B&J.pdf03-1510-0344(Drawing 66473SCS, Century Spring)Observed
Custom Column3(highlighted red) with value2534, rather than the intended custom name.Expected: Custom critical value names defined in assembly mode transfer over and display consistently (per component) rather than reverting to a generic "Custom ColumnN" label.
Screenshot attached below.