cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

A cross-hatch profile should be mapped when a component is replaced in an assy

A cross-hatch profile should be mapped when a component is replaced in an assy

A cross-hatch profile in a drw will not map to a component that is replaced with another family table instance in an assembly. The profile will reset. This can cause issues by releasing a drawing that has the wrong x-hatch.

Response from PTC:

When a component is replaced with one of its family table instance, the ID of that component in the drawing will also change. As a result, the hatch profile property association cannot be maintained. As a result, the hatch pattern will be reset for the new component. This functionality is working as per current product specification.

If references are mapped during the replace, so should the cross-hatch. I almost didn't catch that the X-hatch practically disappeared on me!

1 Comment
Community Manager
Status changed to: Archived