Skip to main content
kimndave91-Visitor
1-Visitor
December 19, 2011
Question

Name, Number, Filename

  • December 19, 2011
  • 10 replies
  • 3706 views


What advantages are there for Name == Number == Filename?


Disadvantages for Name != Number != Filename?

10 replies

Anonymous
December 20, 2011

Are there advantages one way or the other?
It really comes down to your requirements.
In our case, we keep Number & file name the same, and usually the Name as well.
The Name is no big deal, as it is only a title (short description).



Gerry



In Reply to David Schenken:




What advantages are there for Name == Number == Filename?


Disadvantages for Name != Number != Filename?


patrick.chin11-Visitor
1-Visitor
December 20, 2011

Simple:



  • do you want it to look like a mess: Name=number=filename

  • or do you want specific attributes to dentify what they mean: number=doc_name name=PTC_common_name filename=doc_name+ext

  • Do you want it to look like a BOM with proper populated:number=doc_name name=PTC_common_name filename=doc_name+ext

  • Do you want it to match WTPart: number=doc_name name=PTC_common_name filename=doc_name+ext

  • Best practice forward and future WTPart implementation: number=doc_name name=PTC_common_name filename=doc_name+ext

  • no redundant attributes: number=doc_name name=PTC_common_name filename=doc_name+ext

  • no application customization: number=doc_name name=PTC_common_name filename=doc_name+ext

  • no data cleasing required: number=doc_name name=PTC_common_name filename=doc_name+ext

  • 100% migration with the simple fix attached from Pro/I's and other CAD tools.

proed1-Visitor
1-Visitor
January 6, 2012

Hi folks


We've got the name and number working as we want with Pro/E and Windchill PDMLink, using autonumbering and the preferences below:
Upload Drop Name File Extension YES
Upload Drop Number File Extension YES


However, the name is still editable, so people could type anything in there - we'd rather keep it fixed to the autonumber.


Question: anybody know how to do this simply? PTC have described a complex-looking J-Link customisation, just checking if there's not a simpler way.


Thanks for your help!


Edwin Muirhead, CAD Manager, Weatherford

MikeLockwood22-Sapphire I
22-Sapphire I
January 6, 2012
Why would you not use the Name field for something descriptive (e.g. Bracket...)?
LewisLawrence13-Aquamarine
13-Aquamarine
January 7, 2012

Mike,


The goal here is to prevent changes to the assigned EPMDocument number.


The issue currently is that when a user creates a new model in their workspace, the "Name" field is editable, and whatever value is used then becomes the EPMDocument number on Save/Upload. The EPMDocument number should remain the assigned (C001234567) value. Any descriptive info will be going in the "Common Name" field, which then becomes the EPMDocument name.


If a particular filename is required other than the assigned number, then that update can be made after creation as a separate update. Ideally the "New" screen in Pro E should have three fields, Number (which is un-editable), Filename and Name.


Any suggestions for forcing the user to keep the system assigned number on the EPMDocument?


Is it possible to only assign the number on save/upload?


In Reply to Mike Lockwood:


Why would you not use the Name field for something descriptive (e.g. Bracket...)?
ptc-8104501-Visitor
1-Visitor
January 9, 2012
Hi Lawrence,
In our system (WC 9.2, WF5), the filename field is autopopulated with the
next available number and the engineers are instructed not to change it
(even though it is editable). This works most of the time. Usually when
it doesn't is because the engineer is uploading files created by
contractors. In this situation we renumber the files (this can be done by
renaming the file, and clicking on Set New Name then Auto Number as shown
below). The drawing Reviewers / Approvers ensure that drawing numbers are
correct (they are displayed on the drawing so it is very easy to check).




Regards,
--
Mark von Huben

Cochlear Ltd
1 University Ave
Macquarie University NSW 2109
Australia



MikeLockwood22-Sapphire I
22-Sapphire I
January 9, 2012
Does attached provide any more useful info?
proed1-Visitor
1-Visitor
January 10, 2012

Thanks Mike and Mark for your replies.


We're pretty happy with how the Name and Common Name operate (it may be useful if these names were named differently!) - and will train people to leave the Name as-is and type the description in Common Name.


Like Mark, we may have to rely on people leaving the autonumber if we can't find a software method of freezing it.


I'm hoping Creo 1 or 2 will have an option for this, maybe find out something in Boston this month.


Cheers
Edwin

proed1-Visitor
1-Visitor
May 4, 2012
cc-21-Visitor
1-Visitor
August 20, 2012

Hi


a lot of things have been said on Name, Number, Filename.


One thing I have not seen is about data integrity with other system such as ERP


Would you have number and name/description being the same ? I do not think so, so in PDMLink this is the same.


In addition, if you link (manually or automatically) Windchill to an ERP you would want a 1 to 1 relationship. That is PDMLink Number = ERP Number and PDMLink NAME = ERP NAME/Description.


Now, why is ProE not showing Number and Name (and eventually Filename) in the New Window in ProE


As far as I understand it. ProE was created well before PDM/PLM. At that time of file servers. things were done by filename. Name in ProE meant filename. When ProE got integrated into PDMLink , this window did not change. Why ? I guess there are still plenty people using ProE as standalone software still.



We have been implementing sequential number and moving from descriptive number. To prevent people to change the field Name (ProE, ie Number in PDMLink) auto populated, we wrote a small little java custom rule associated with the OIR.


So technically, people can change what the system put in Name (ProE window) but will not be able to upload their file... Causing them all sort of headache,. so they do not touch that field anymore.



Terms & ConditionsAccessibility statement