Skip to main content
P
pcnelson1-Visitor
1-Visitor
March 11, 2013
Question

Use ModelCheck to synchronize Name, Number, File Name?

  • March 11, 2013
  • 1 reply
  • 782 views

My company would like all three fields to be identical; Name, Number, File Name. Is there a way to use ModelCheck to verify this before a Save or Check-in? Thanks


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.

1 reply

A
Anonymous
March 25, 2013
Name & Number are depending upon your mapping in your EPM object type.
Typically, PTC_Common_Name is used to derive Name, While the file name
is used to drive both file name and number.



PARAM_NOTE_REQ might be able to do what you want (verify that
PTC_Common_Name equals file name). But since it needs to be a variable
(i.e. &file_name) I'm not sure it will work on the Creo side. Note, once
the file is uploaded or checked in, you will have to make the change in
Windchill as Creo will no longer let you change it.



On the Windchill side you will need to implement ModelCHECK Gatekeeper,
which if you can get PARAM_NOTE_REQ check to work for you then the
gatekeeper is easy.



There is another tool I've been playing with lately that can do the
check for you, I just don't know what integration functionality it has
with Windchill. (I know it has some, just not the specifics). Model
Processor from INNEO (modelprocessor.inneo.com). This is what the one
function for editing the PTC_Common_Name looks like (other report types
functions from MP may be preferred though);











Dan Harlan
Mechanical Engineer / CAD Administrator
480.940.0036 x178 Office
480.940.0039 Facsimile



481 N. Dean Avenue
Chandler, AZ 85226
dharlan@aitint.com
www.aitint.com






Terms & ConditionsAccessibility statement