Skip to main content
Oct 9, 2012 10:32 PM UTC
Archived

Better Description of Models & Masterdata (special characters, counters, etc.) - was "Automatically recognize changes in capitalization from models to add spaces to the Model description in the model save dialog."

Related products:Creo Parametric

When saving from Modeling to ModelManager the save dialog has the Description populated with the Name from Modeling, but before saving new Models/Masterdata we need to go through and add spaces to separate a long text string into a series of words. It would be a great efficiency benefit if it were able to identify shifts from lower case to upper case and add a space at those points.

 

It also might be cool to strip .01 off the end of the names.

 

This may need to be parameterized since some people may separate their words using periods of underscores rather a change in case.

 

ModelManagerSaveDialog.PNG

6 replies

Oct 10, 2012 6:44 AM UTC

The source of this idea is that it is not possible to put many special characters (: * ? < > | [ ] \ / ' " ; = + % $& ~ ! # @ ^ ,), even the space in the part name. I understand that some characters can by considered by Modeling as very special such as "/", but why the space ?

In the help pages, it is said that these characters are forbidden because of file name and shell scripts. In modeling v18, is there still a connexion between the part name and file name or shell scripts ?

It should be possible to insert such characters (except "/").

Note : in Drafting, it is possible to use all the characters except "/" and "~".

Oct 10, 2012 3:03 PM UTC

Good point. I guess I might actually prefer just being able to have my description already be formatted in Modeling the way I want it formated in Manager. The one downside is that by using spaces my Structure Browser will need to be wider for me to be able to see the whole name - but that's probably a small price to pay.

Besides the space the special characters I most often want to use are comma, Ø, #, and /:

"#4-40 x 3/4 Lg Socket Head Cap Screw"

"Ø1/8 x 3/8 Lg Dowel Pin, SS"

So if we're changing the use of special characters can we make \ the exception and allow us to use /?

Perhaps you should make that an idea - rather than a comment so we can all vote for it.

Oct 10, 2012 3:14 PM UTC

The last piece of the naming convention to clean up would be using ".1.2.1" appended to the end of the name. Can there be another column perhaps that is a counter? I'm guessing that to a make new naming conventions backwards compatible it would have to be a new field of data (perhaps descriptive name), and the current name field within Modeling would be relegated to hidden (optionally visible) status. If it's a new field it wouldn't have to have any limits on special characters. Perhaps the original Name Field, and the new Descriptive Name and the new Counter fields in Modeling could be somewhat analogous to the Unique ID, and Name/Rev in Modeling (although there'd be no need in my mind to be strictly enforced the way Unique ID is).

The new counter field could have a column heading of just # so that it wouldn't take up much width in the structure browser.

Oct 11, 2012 7:37 AM UTC

Greg,

I do not think that another idea is necessary. I think that this question is to be treated generally because part name and masterdata description are more or less linked :

- Part name syntax

- Masterdata description syntax

- Standard rules and customized rules for transfering part name to masterdata description.

Apr 24, 2013 6:50 AM UTC

I Think that / and \ both are special characters and so they cannot be allowed to be used in part names.

eg. / is used as separator in paths inside Modeling.

Both characters cannot be uses in filenames.

I would suggest to allow all characters which are allowed in filenames.characters+not+allowed+in+filenames.png

Precisely spaces should not make problems.

Mar 16, 2019 1:58 AM UTC
Status changed to: Archived