cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Organization based unique CAD file naming constraint

Organization based unique CAD file naming constraint

Current market conditions drive us to have multiple Organizations based on the type of busines domains like Automotive, Computing and soo on. The file names are either driven by the Customer or by the standard naming conventions. The file names are pretty much same across Organizations but the contents in it like Parameters, Co-ordinate systems, tables, symbols are different between each Organization. So the CAD file is actually different, but having the same name across Organizations is not feasible in Windchill. Hence a property to enable unique file naming constraint at Org levels should be provided. This will help us to have unique file names at site level or at Org level.

6 Comments
Emerald I

If you NEED to do this today and don't mind hacking the database, there may be a solution in this thread at PTC User:  http://portal.ptcuser.org/p/fo/st/post=124717&anc=p124717#p124717

Regular Member

Tom,

Do the proposed customizations support non-unique file names or just non-unique business object numbers, by extending the definition of uniqueness?

We take in a great deal of files  from various clients, and often have clashes on file name. Can't import bolt.prt from client B because unrelated bolt.prt already imported from client A. This is perhaps the number one complain from our users. I have heard rumors that some rival PLM systems don't have such a problem with this. I don't know how true that is.

Darren

Emerald I

I don't know.  I just remembered the discussion about this and wanted to share the link.

Thanks for the inputs. Yes few PLM's / PDM's do allow this, I have seen this in Infor PLM, Solid Works ePDM. I think this should be given as a preference in each Organization within PDMLink.

Satheesh

Yes Darren, some PLM vendors provide have same file names. It would be if PTC can also support this, and differentiate having different EPM Name and Number

Community Manager
Status changed to: Acknowledged