Community Tip - New to the community? Learn how to post a question and get help from PTC and industry experts! X
Version: Windchill 12.1
Use Case: Trying to map NX model attribute/property to the NX drawing file
Description:
Using the master model system in NX, where the model data is in one file, and the drawing data is in another file. The attribute/property DESCRIPTION is entered in the NX model file, and mapped to Windchill, so it can be displayed in a column in WGM. In the drawing templates, we use DB_DWG_TEMPLATE_DESCRIPTION to map this attribute from the NX model file to the NX drawing file, for use in the drawing format title block, but this does not work to populate the DESCRIPTION attribute/property in the drawing file. For that we have to manually copy it, type it, or link it via inter part object attribute. We would like to automate this, to prevent errors, or simply forgetting to do it.
When forgotten, it looks like this in WGM:
We do have PTC_WM_IS_DRAWING set to "true", so Windchill should know it is a drawing, vs. an assembly.
How would we go about mapping this? Do I need to use a different attribute/property in the NX drawing file, so somehow pull in the DESCRIPTION attribute from the model in Windchill?
On the Windchill end do you have an attribute at the EPMDocument type set for the Description?
When you set up your drawing template, did you set up the attributes to pull from it's associated master model?
First question, I think so. I'm not the Windchill admin, but I know Windchill pulls the DESCRIPTION from the model file, to display in the WGM as DESCRIPTION_PME (we use multiple CAD systems, Creo was already using DESCRIPTION).
Second question, yes, I'm pulling various attributes from the NX model to the NX drawing for use in the title block with the DB_DWG_TEMPLATE_ attribute mapping method.
Have you looked through this documentation on Configuring Windchill Attributes with NX?
There's a difference between the system attributes (Windchill defines, those. Things like Name, Number, PTC_WM_IS_DRAWING that you're already using) and custom attributes.
For description (defined at the parent EPMDocument type level on your admin side of things), you can define which attribute name on the NX side maps to that Windchill attribute. Creo and NX can have different values there (see this page from the above link).
To have the same attribute then be used on the drawing, you use the attribute name as defined in the model on your drawing template where you want it to show up. I normally have all of that be driven from the model side so the drawing ends up just being a collection of imported model attributes.
Thanks, I'll do some more reading.
For what it's worth, I'm not using the DB_DWG_TEMPLATE attributes anywhere on my end in Windchill.
Also: make sure that your drawing template in the ug_drawing.pax is setup correctly for multiple sheets.
How so? Our base drawing template has 2 sheets, since sheet 1 has the full title block, and sheet 2 (and beyond) use a smaller title block. I have ugs_drawing_templates.pax and ugs_sheet_templates.pax setup the same way I've done it for years, and I've never really done anything special for multiple sheets.
DB_DWG_TEMPLATE_ is how I've done it for years too, so I never thought about doing it any other way, although I'm sure you could use attributes mapped thru Windchill, I've just left Windchill out of the equation as much as I can.
Our old templates had all sheets set up in the .pax file as "DrawingTemplate" objectdata class type and that caused for issues on all sheets except for the first one. "SheetTemplate" is the way to go.
I went the other way and mapped everything to Windchill that needed mapping there. You said you don't have access to Type Attribution?? That's really your ticket to get data to show up on the Windchill end that you define on models and/or drawings.
Hi @Dave_K,
I wanted to see if you got the help you needed.
If so, please mark the appropriate reply as the Accepted Solution. It will help other members who may have the same question.
Of course, if you have more to share on your issue, please pursue the conversation.
Thanks,
Anurag