Inventor parameters - Case sensitive?!

[CCarreiras]

Hi!

Using Inventor 2026:

- I created two parameters in a part: A_ and a_

- Next i would like to compose the part Number based in those parameters, something like:
"Part - A_ x  a_"

...BUT... seems like the system is ignoring the uppercase and lowercase letters, and the end result is always "Part - A_ x  A_" or "Part - a_ x  a_"

Pretty sure that this worked in previous versions.

So, my question is... Inventor 2026 is not case sensitive anymore?!
And if so, Autodesk wonders how many parametric systems already done in previous versions can be damaged because of this?!

...or is just a fixable bug?(i hope so)

Here's an example:

The part is attached to test.

[johnsonshiue]

Hi Carlos,

If I recall correctly, the parameter names are always case sensitive, while Custom iProperties (or iProperties in general) are not case sensitive. It is on first-come-first-serve basis. When there are two parameters with the same name but in different cases, the first one gets exported will be shown in the Custom iProperty dialog. This behavior has not been changed.

I personally think it is better to always treat Parameters as case insensitive, particularly exporting to custom iProperties. It can easily lead to confusing behaviors.

Many thanks!

[CCarreiras]

Thank You @johnsonshiue .

I also recall that the name parameters used to be case sensitive, I'm not sure about the custom parameters.

Thank You anyway.

I have to be careful if i need to turn a parameter into custom parameter.

[johnsonshiue]

Hi Carlos,

I am sorry I probably did not explain the behavior clear enough. The property expression formula in "Part Number" (or any iProperty) is based on the iProperties, not the parameters. In your case, <A_> and <a_> are from custom iProperties (exported from Parameters dialog). As I mentioned earlier, iProperties are case insensitive while parameters are case sensitive. As a result, the custom iProperties list only shows <A_> or <a_>, depending on which parameter was exported first.

It is possible <A_> and <a_> both exist in the database (one might be corrupted), which is why the value still shows. Regardless, having mixed case names can be confusing. I have seen corrupted files due to the usage of mixed case names. The behavior can be reproduced in 2020 also.

Many thanks!