Importing expressions into a drawing specification?

[LinuxFreak]

For several years we've been importing expressions (output from Excel) to drive our models. However, for those years we've had our drawings embedded in the same part files (Teamcenter context). Those drawings also referenced some of the expressions imported into the part file. Now we wish to use separate specification drawings, though still within the same Item revision, and importing the expressions (for multiple parts simultaneously) fails as I can't figure out how to tell NX what the part name is for the specification.
For a simple example, here's an expression file with two expressions, one for the part and one for the specification. The one for the block imports fine. It doesn't seem to need to know the specific revision one is working in. However, the portion that I need to go into the specification fails as it can't find the part (both the model and the specification are loaded in NX of course). I've tried several variations on the formatting of the specification name, but still no success. I'm trying to avoid having to import several separate expression files while making each specific part the work part. What would be the proper syntax for the specification name?

[pre]#--------------
!1234567-BLOCK
#--------------
(string)VENDORNAME="Vendor Name"

#--------------
!1234567-BLOCK:s:1234567-BLOCK-A-DWG
#--------------
(string)CUSTOMER="Customer Name"[/pre]

Windows 7-64 / Core-i7-4800MQ / 16GB RAM / Quadro K2100M
NX 10.0.2.6 / Teamcenter 10.1.3.2 / ANSYS 16.1

 

[JohnRBaker]

Try creating 'Interpart Expressions' to link expressions for one part file to another.

John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Digital Factory
Cypress, CA
Siemens PLM:
UG/NX Museum:

To an Engineer, the glass is twice as big as it needs to be.

 

[LinuxFreak]

@JohnRBaker

I have done that with a few expressions, and could carry on with that approach, but Interpart Expressions can sometimes lead to other issues down the road, such as when parts are cloned or Saved As. Since there's not that many expressions we use in the drawing specification, I guess I'll carry on with Interpart Expressions. Just thought there'd be an easy way to distinguish between the UGMASTER dataset and the UGPART dataset when importing expressions.

Thanks John.

Drew

Windows 7-64 / Core-i7-4800MQ / 16GB RAM / Quadro K2100M
NX 10.0.2.6 / Teamcenter 10.1.3.2 / ANSYS 16.1

 

[cowski]

Perhaps attributes would serve you better. All the info could be added as attributes to the model file and the drawing would just reference the attributes.

www.nxjournaling.com