Long requested... Remove the limit of 31 characters in creo file name If you have maintenance, you can vote on the product enhancement request.
This has been in the planning for a long time with no implementation in sight.
How many PTC programmers does it take to fix the length of the name field?
32, but only 31 work.
I appreciate the replies... I know this is a duplicate complaint. I just needed to rant about it since, at the moment, it's interfering with my job, once again.
With 26 alphabetic characters, 10 digits, and the underscore you have only 37^31 possible names or 4113897303606771042156868599311296618503721408813.
Did you run out?
It's an easy limit to hit when making filenames into encyclopedia entries covering revision history and routing and material and who worked on it and what the release level is and so many other non-name factors.
The good news is they are apparently going to increase the limit, but I shudder to think of looking into a model tree with part names of 512 characters, or maybe 1024 just to be sure.
Yes, I ran out.....I got to part number 4113897303606771042156868599311296618503721408814 and had an error.
I know you're trying your best to belittle me or others who might have issue with the limit, but there just might be other issues that you haven't considered.
No, I (we) don't use such long filenames for parts or assemblies we create for our database at my job. I think such long filenames are silly, too.
However, as you may or may not know, dealing with customer CAD many times requires much longer filenames. Having to truncate them to be friendly with our database is often time consuming, and shouldn't be necessary at all... hence my original rant/complaint.
Here is an example part number from an automotive manufacturer I deal with (yes, underscores, and all):
Imagine hundreds of these part numbers for a larger assembly.... maybe now, you understand.
A 31 character filename limit is ridiculous. Yes, this is a repeat complaint, but it's still not fixed in the latest version of Creo...unacceptable.
Long file names are why databases where invented with search tools.
Keep the actual file name short and meaningless. Make the Common Name something intelligent and use the search feature to find the cross reference.
At one company we were discussing how long to make the filename field in the database and the longest name we came up with was like 26 characters. That was for a secondary NC program filename where we used the revision and NC machine code with operation number in the name. For our standard engineering part numbers, we only needed 18 characters and those were also a special use naming. The corporate 'standard' file name was 7 characters in length. We had spent 6 hours with people from 8 divisions discussing how long to make them. We finally settled on 64 characters, just to please everyone and allow transitions when companies were acquired.
It seems logical to keep filenames short and meaningless.
And I assume this is also how PTC intends it, as they provide means for an auto generated number for the file name, and also expect the file name to be unique:
What I do not understand however, is that they then use the (meaningless) file name as the primary identifier in all other dialog boxes and info pages, e.g.:
File - open dialog:
How is one supposed to know that 0381212444.asm is the actual assembly to be opened? It's a meaningless name.
In this case, one can argue that the correct procedure is to search in Windchill instead, and select "Open in Creo".
But the same goes e.g. for the "assemble" dialog box, which is identical to the "File - open" dialog. I don't know an alternative for this straight from Windchill...
Also e.g. in Windchill:
The Common Name is shown under "CAD Document Attributes", but all the other fields refer to the file names, e.g. also in the structure view. I know these views can be customized, but it really wonders me why on the one hand it seems to be intended that file names are meaningless, auto generated numbers, and on the other hand in the standard Windchill layouts, the file names are used as the main identifiers...
Also the model tree shows these "meaningless" file names. I know the Common Name can be added as an extra column, but this takes up valuable screen space, and is IMHO less readable (e.g. not in the leftmost column, not indented, etc):
In a company I worked for previously, this was 'solved' by giving a readable file name to each 3D component, instead of a "meaningless" number.
They had a customized 'file - new' dialog, which checked for file name uniqueness, and added some random characters to the end of the file name to ensure this uniqueness (hereby limiting the nr of characters to even less than 31...).
I think this is the way we will also go, albeit without the customisation. Only real drawback I see is that, without this customisation, you only know if the chosen filename effectively is unique upon check in. Which probably also will be annoying but I don't see a better solution currently...
It's been over 16 years since PTC purchased Windchill and it's still not properly integrated with Creo. There are many, many product ideas on this community highlighting these differences with the goal of getting them fixed but unfortunately there hasn't been much progress. These fields and their usage are core to both Creo and Windchill and changing them so they actually agree and make sense is going to take a bunch of work for either the Creo developers or the Windchill developers. Unfortunately the current approach seems to be to leave them both alone and just live with the poor integration. Keep in mind as well that making these agree with each other isn't going to sell any new software, so this greatly reduces the motivation for PTC to actually do something about it.
It's hardly belittling to point out the lack of need for a feature, though perhaps your customer should feel ashamed of encoding a good portion of their process management into plain text. 22032010 looks like a day-month-year, for example. could be reduced to 3 ascii characters instead of 8. Dashes could be used to terminate fields so that empty "_"'s were not required to align fields.
I can't fix Windchill, Creo, or your customer, so don't belittle me for expressing my own clearly marked not-all-about-you rant
I can suggest that in order to handle your customer, you use a hash function on the original name. This will reduce the lengthy name to any number of characters, and 31 will be plenty. To decrease the odds of collision, add a random number to the customer number that is generated with the date field as the seed value so it will be repeatable. The original name can be stored as a parameter that is declared to Windchill, if you like, so that Search can find ir. By using a hash with a seed, it isn't absolutely required to keep a table of all the conversions; any component file that is opened can be inspected for the original number and any request by customer number can have the hash generated to find the component hash number.