cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Community Tip - You can change your system assigned username to something more personal in your community settings. X

Organization based unique CAD file naming constraint

Organization based unique CAD file naming constraint

Status: Archived Submitted by 1-Newbie on ‎Oct 09, 2014 03:17 AM
7 Comments (7 New)

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.

See more ideas labeled with:
7 Comments
TomU
23-Emerald IV
23-Emerald IV
‎Oct 09, 2014 07:23 AM
‎Oct 09, 2014 07:23 AM

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

DarrenStorey
7-Bedrock
7-Bedrock
‎Oct 09, 2014 07:48 AM
‎Oct 09, 2014 07:48 AM

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

TomU
23-Emerald IV
23-Emerald IV
‎Oct 09, 2014 07:55 AM
‎Oct 09, 2014 07:55 AM

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

SatheeshSukumaa
1-Newbie
1-Newbie
‎Oct 14, 2014 01:45 AM
‎Oct 14, 2014 01:45 AM

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

SatheeshSukumaa
1-Newbie
1-Newbie
‎Apr 24, 2015 02:52 AM
‎Apr 24, 2015 02:52 AM

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

PTCModerator
Emeritus
‎Jun 11, 2018 01:59 PM
‎Jun 11, 2018 01:59 PM
Status changed to: Acknowledged
 
olivierlp
Community Manager
Community Manager
‎Jan 05, 2022 09:15 AM
‎Jan 05, 2022 09:15 AM
Status changed to: Archived

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.