Skip to main content
Aug 3, 2021 10:16 AM UTC
Archived

Toolkit APIs calling parameter names returns Component names in upper case only.

Related products:Creo Parametric

most of Toolkit APIs like ProMdlMdlnameGet() or APIs calling parameter names returns names in upper case only.

There should a toolkit API to provide the Model/Component names with Case Sensitive.

 

5 replies

Aug 3, 2021 12:03 PM UTC

Within Creo itself, particularly when used in relations, there is no sensitivity to case. In fact, even in relations I've written with the mixed case I defined the parameters with, the code only shows lower case.

For example, if I define a parameter as numParts and make a relation like "numParts = 2 + numAsm", if I re-edit the relations later the equation will be "numparts = 2 + numasm".

So the case of the characters in a parameter name don't really matter in terms of access to values in Creo. The same is true of file names and such, too.

Praveen2Author
Aug 3, 2021 12:31 PM UTC

@KenFarley Yes I agree with your statement that if the name is being used in relations, there is no sensitivity to case.

But I have one auxiliary application where it creates files on the disk with the same name as creo parametric model file name is (of course with different extension).

So user's expectation would be, if he has provided MyTestFile.prt then he would expect MyTestFile.ext and not mytestfile.ext or MYTESTFILE.ext  .

Aug 3, 2021 1:29 PM UTC

The thing is, I don't think Creo even stores the parameters with the mixed case names I enter. I have a part that I built and it had parameters like angLock, DescriptionBOM, DesignBy, diaSlot, htLock, etc. When I open up the Parameters dialog to modify one of the values, they are listed as ANGLOCK, DESCRIPTIONBOM, DESIGNBY, etc. All the nice readable mixed case names are now FORTAN-ish all caps. Any specification of mixed case letters used to define the parameters is lost when they are saved, it seems. It's saved for the parameter values, but apparently not the names of the parameters.

As far as file names go, that has long been an annoyance. The value of rel_model_name() is always returned in all caps, regardless of what the "real" file name is. I guess they'd say "oh, but it's not the file name it's the model name" but then there is no function that lets you get the actual file name.

Community Manager
Feb 21, 2025 11:34 AM UTC
Status changed to: Acknowledged

Hello,

Thank you for your idea. Based on the details provided, we are acknowledging it as the Community management team. This is not a commitment from the Product team.

olivierlp
Community Manager
Oct 8, 2025 3:06 PM UTC
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.

Olivier