Skip to main content
Jul 8, 2012 3:05 AM UTC
Implementation In Progress

Remove the limit of 31 characters in creo file name

Related products:Creo Parametric

31 characters are not enough for design. This limit sometimes is driving customer crazy. For CATIA the limit of file name is 81 characters.

87 replies

Apr 24, 2017 1:34 PM UTC

Just to clarify, I would like to see a larger percentage of the maintenance dollars we pay go towards fixing existing open issues and less towards adding new functionality (that somehow we still end up having to pay extra for.)  Having core functionality SPRs still open after 10 years is very frustrating.

Apr 26, 2017 11:35 AM UTC

Let's say for a minute that PTC actually does release a major revision of just bug fixes.  There is no way they can fix ALL the bugs.  Even if they do 2 or 3 major releases of just bug fixes.  But that isn't realistic.  Creo is just too huge.

Let's also say they got the bug list down substantially.  You don't think that will just start all over again where the bugs list goes back up?  If there are new features then there will be new bugs.

Apr 26, 2017 11:55 AM UTC

A guy can hope, right? 

When the new features from 15 years ago are still only partially implemented, the development focus seems to be out of balance.  (How many places can you still find the menu manager?)  There are many, many basic usability and functionality issues that people have been struggling with for many years that never seem to get addressed.  (Just review the thousands of ideas on this community.)

Concerning this specific idea, Microsoft introduced long file name support back in 1994 (23 years ago!)  I believe Creo became a Windows only product back in 2002 *.  15 years later and Creo still doesn't support long file names.  Can you think of any other non-PTC software for Windows that doesn't support long filenames?

* Correction.  PTC dropped support for Linux with Wildfire 4.0 (2007) and dropped support for Solaris with Creo 1.0 (2011).  Creo 1.0 was the first release that was only supported on the Windows platform.

Apr 26, 2017 2:51 PM UTC

Can a guy hope?  ABSOLUTLY!  I would love to have a bug-only revision too.  But as Stephen W said...it doesn't bring in the sales.  How about PTC using the digit AFTER the dot for bug-only releases.  2.5, 3.5, etc.  Why do they even put the .0 afterwards if they don't use it?

Jun 14, 2018 6:11 PM UTC
Status changed to: Acknowledged
Sep 20, 2018 9:51 PM UTC

When working on this, please do not for get to allow for more than 31 characters for the ".sym.1" (drawing symbol files).  It only allows 31 characters and thankfully doesn't include the decimal to the end (in this case 6 characters for the .sym.1).

Oct 8, 2018 2:28 PM UTC

I wonder if some of this can be solved by using the Description parameter?

How about implementing a more limited scope work-around in the mean time by improving the visibility of the Description?

  • Make the Description parameter visible in the Open, New and  Save dialogs. (writable as appropriate)
  • Whenever IMPORTED files have their file names truncated to 31 characters, put the original file name in the Description parameter.  This is a big one that would really help anyone importing these longer file names. Of course it could be any parameter, but preferably one you can show in the assembly tree column like Description.
  • Add the Description to Model Information.

I believe at some point the information in long file names should be placed in a description instead, or other parameter fields, rather than longer and longer file names. 

 

Also please consider this, that when renaming an assembly, file names at the 31 character limit make it difficult to append a job or project number suffix.  It would be nice to be able to perform some sort of auto-name-shorten to make room.  If you do it like long file names are truncated to 31 characters, only let it be shorter like 27 characters, then the suffix can be added without exceeding 31 characters.

Oct 19, 2018 11:26 PM UTC

Description is a good place for information when it makes sense.  Some factors why the long file names may still be useful

  1. We don't store symbols in WC at this point so there is no description! 🙂
  2. Legacy data
  3. If you are saving an email with a longer file name, it may very well contain very useful and recognizable data that you don't want to truncate and then also run the risk of having the same filename as another file in WC and then have to figure out a new name.

 

But I agree that the description field is a better place for detailed information in a lot of cases...just not all.  From a user perspective, I just don't see a reason to maintain the 31 character limit.

May 7, 2019 12:47 PM UTC

Creo 4 still only allows 31 characters in the file name.  I thought it was supposed to be changed.

May 7, 2019 1:12 PM UTC

06/14/2018 note in this thread only says that PTC has acknowledged this request. That was AFTER Creo 5 was released. With the major/minor releases, We can only hope this change makes Creo 7 or it may not make it until Creo 10! I can see this being an enhancement that the big companies want, or maybe not since most big companies use Windchill.

Community Manager
Sep 19, 2019 4:44 PM UTC

31 characters are not enough for design. This limit sometimes is driving customer crazy. For CATIA the limit of file name is 81 characters.