Revit automatically chooses to uncapitalize shared parameters

[m-de-lange]

To keep our projects neat we have all parameters written with a capital first letter.

Unfortunately Revit decides for us whether it wants the parameter capitalized or not, once we added it to the project parameters.

For example, we have a parameter named Armatuurcode. When we add it as a project parameter it becomes 'armatuurcode' Thus making the list look messy and unprofessional. This only happens to certain parameters.

What could be the cause of this?

[iainsavage]

Are they definitely the correct parameters loaded from the correct shared parameter file and not duplicates maybe created in an older version?

I’ve never seen behaviour like this. I usually use all caps for my parameter names to distinguish from standard Revit and manufacturer’s parameters and never had an issue with Revit changing them.

[m-de-lange]

We have added this and the other parameters before with uncapitalized first letter.

Though, even when i remove that parameter Revit still forces the first letter to become uncapitalized.

And yes i'm sure i'm using the correct parameter from the correct file. You can literally see Revit change it upon adding the parameter

[iainsavage]

If you start a new project from a completely blank “none” template and then load those parameters does the same thing happen?

[m-de-lange]

No then it's right.

What does this mean? Somewhere in our template revit remembered that it had the parameter 'armatuurcode' added before and refuses to do it the right way?

[L.Maas]

How did you change the shared parameters? Did you change the original parameter or did you create new ones?

Are there things in the template that have the original shared parameter attached? 

Not sure if it would whelp, but if you do a save as on the template and then check "Compact File" see if that has an impact.

It is always tricky when renaming shared parameters, might give weird behavior. So maybe it is best to start with a clean template anyway to prevent these present and future issues.

[m-de-lange]

We renamed all parameters in the .txt file.

After that i deleted the parameter as project parameter, then i tried re-applying them from that same text file. But then they end up uncapitalized. The parameter isn't applied anywhere else but as project parameter.

So there shouldn't be any other options that would force Revit to uncapitalize it upon adding the parameter.

[fabiosato · Accepted solution]

Hello,

RVT file is keeping track of the original GUID of the parameter, maybe creating a new one with a new GUID will be safer.

[m-de-lange]

Replacing the entire parameter is not an option here

Any other way that would work?

[L.Maas]

As mentioned, renaming parameter is risky. As you already noticed, some things are still remembered even if you think you removed all. If things go wrong with shared parameter it might create havoc on your project(s). Therefore the recommendation keep being not to rename the shared parameters in the shared parameter file. The proper procedure will be to create new shared parameters and use those.

In those cases the procedure would be:

1. Create new shared parameter(s)
2. Add shared parameter(s) to project/families
3. Map data from old to new (manually or using an add-in or using Dynamo)
4. Verify process Ok.
5. Remove old shared parameter(s)

Again renaming shared parameters is asking for problems.