#Ug nx 10 tutorial manual

Siemens Product Lifecycle Management Software Inc. NX Product Manager, Knowledge Reuse and NX Design Presuming you remembered how all of the IPEs were hooked up before.ДЄnd so in the end we're SO wary of creating this problem in our customers' assemblies that we've actively chosen NOT to provide a utility to renumber expressions.ДЄnd so if you choose to pursue this with automation anyway, beware.

#Ug nx 10 tutorial manual

and which would require some manual re-association of the broken IPEs to fix.

? <- With an IPE 'source'::p68 now BROKEN Or even worse, if you've started with a situation like this: which may no longer be there, in which case the IPEs will be put into a 'broken' state in NX 10+ (the last known good value cached, waiting to be directed to a new parent) or converted to a constant value (with the interpart reference deleted entirely) in versions prior to NX 10. And in that situation, if you rename expressions in the source part, the downstream referencing parts will not know about that change.ДЄnd so the next time you open those downstream referencing parts, the IPEs there will still be looking for the old expression names. (And yes, if the referencing parts are open in the session, then we can very easily tell you whether an expression is being referenced or not.)Д«ut it's pretty easy to get into a situation where you've got a source part open, with one (or some, or all) of the downstream parts containing IPEs that reference expressions in that source part NOT currently open. As such, it's difficult to predict where expressions are being referenced unless all of the potential downstream referencing parts are open in the NX session. Interpart expressions (IPEs) are a pretty simple 'pull' or 'reference' relationship, where the 'referencing' or 'destination' part retains a reference to the 'source' or 'target' part, but not the other way around.

The biggest opportunity for nasty problems here is interpart expressions. As SPLM, we've actively resisted providing a utility for this, because there are some pretty nasty side effects if the end user doesn't approach this perfectly.