Interpart Expressions

[RKulchy]

Is there a way to wildcard interpart expressions?

For example, I have an assembly with 10 parts in it. Each part has some interpart expressions to the assembly. When I adjust the expressions in the assembly to drive the design of the parts I want to be able to save that particular configuration as a new assembly. Even though visually it looks correct in session, once you close everything and reopen the newly created assembly file, the configuration is not correct as the interpart expressions are linked to the original assembly file. I dont want to have to go through and manually edit the part files or the new assembly file as this new file is a one off and would never be touched again.

If there is possibly a different way of achieving what I am trying to do or a better way please let me know as well.

Currently using NX9.

Thanks for any help.

 

[MFDO]

First you have to clone the assembly and its components with a unique names or the entire assembly to different location. Then edit the expressions and the new children will follow the new parent.

Michael Fernando (CSWE)

http://www.solidCADworks.com

Tool and Die Designer
Siemens NX V10.0 + PDW
SWX 2013 SP3.0 X64
PDMWorks 2013
Logopress3
FastForm Advance
FormatWorks

 

[RKulchy]

I am trying to avoid cloning the children though. I dont want to create a bunch of unnecessary parts for something that is a create and forget assembly essentially. The only reason I want to save a particular configuration is so we can go back and look at it at a later time if need be.

 

[cowski]

How are you creating the new assembly?

www.nxjournaling.com

 

[RKulchy]

I have a master assembly file that I am using to drive the design of a bunch of sub-assemblies. Once I set the expressions for the configuration that I am looking for I would like to do a saveas to a new assembly file to save the configuration. Once that is done the file will never get updated again; just opened and inspected for various reasons.

 

[daluigi]

Export the assembly expressions to a named file to capture that specific configuration.
You can then import the expressions back when needed to evaluate what the assembly looked like at that time.