set datums in drawing not movable

[ptc-218373]

I'm suddenly having problems in moving set datum tags in drawing views. I've created them in the model, I'm able to see them in the drawing views, but when I highlight them, there are no handles to allow me to move them around - although it works ok in WF4. Anyone know what's wrong?

WF5, M020; Dell M6300, XP-64

Dave Tate
Keystroke Designs,
Kelowna, BC

This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

[ptc-218373]

Well, I got no responses except a question, but I solved my problem (kinda):

I'm working on a detail drawing of the machining of a casting, and the way
it's modeled is: one part for the rough casting (A) which has its own
drawing; a second part with an external merge for the machining (B); and a
utility assembly that combines both parts, which I've used as the model in
the drawing of the machining part B. I like this because I can change the
component display of casting A to be Phantom Transparent and it's outline is
useful information for the machinist. All dimensions are Shown, not Created.
All works well except for the moveably of the set datum tags, which appear
(from part B) - these were created as planes; a datum axis that I attached
to a dimension had no problem in being moved.





The workaround was to retain the datums in the part, but to duplicate them
in the assembly also. These assembly datums can be moved, but the part ones
cannot (which I have to Erase from the drawing views), no matter which model
is set active. The GD&T tolerancing references the part datums correctly,
but those visible in the drawing are the assembly ones. I just have to make
sure I keep the names identical.



This has got to be a bug - Or am I attempting something that isn't good
practice? Is there a better way?



Dave.