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

Community email notifications are disrupted. While we are working to resolve, please check on your favorite boards regularly to keep up with your conversations and new topics.

Unexpected relation change with injected PTC_MODIFIED parameter

jmills
1-Newbie

Unexpected relation change with injected PTC_MODIFIED parameter

This thread may overlap into Windchill if I understand the purpose of the part level parameter PTC_MODIFIED. We have a part where one of its feature level relations was altered by Pro/E (possibly Windchill involved). It altered a feature level relation like so - it substituted a real number part level parameter that was within the relation with the boolean part level parameter PTC_MODIFIED (a boolean and system controlled param). We've seen this in Wildfire 5.0, with at least 2 datecodes M010 and M020. We don't know exactly when it happens, just that some times we try to open the model and Pro/E complains a relation is bad (bad because what was a calculation with a real number is now trying to act on a boolean), then another time the model is opened it is fine. If the model is saved in the bad state and reopened, things can go haywire - opening the parameters editor blows up Pro/E most times, Pro/e can lock up and even the Windows desktop will stop repainting. This happens on multiple machines. There's a PTC ticket on the issue, but it's taking a while. Any ideas? Users are usually working within Windchill workspaces.
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.
0 REPLIES 0
Top Tags