Shared parameters changing names when loaded into project

Shared parameters changing names when loaded into project

Anonymous
Not applicable
5,303 Views
37 Replies
Message 1 of 38

Shared parameters changing names when loaded into project

Anonymous
Not applicable

I'm using a shared parameters file that our firm obtained from a third party Revit Training group. I've been using this to build families.

 

A problem I'm running into is that for certain shared parameters, once loaded into a project, their name changes. I have a parameter named "321Voltage" but when I load it into a project, it changes to "Voltage". Now there are two "Voltage" parameters in my project. The same happens for some other parameters as well.

 

What could be causing this behavior and how can I correct it without recreating the entire shared parameters file? (it's quite sizable and well organized)

0 Likes
Accepted solutions (1)
5,304 Views
37 Replies
Replies (37)
Message 2 of 38

barthbradley
Consultant
Consultant

@Anonymous wrote:

I'm using a shared parameters file that our firm obtained from a third party Revit Training group. I've been using this to build families.

 

A problem I'm running into is that for certain shared parameters, once loaded into a project, their name changes. I have a parameter named "321Voltage" but when I load it into a project, it changes to "Voltage". Now there are two "Voltage" parameters in my project. The same happens for some other parameters as well.

 

What could be causing this behavior and how can I correct it without recreating the entire shared parameters file? (it's quite sizable and well organized)


You have families in the project that are using a Shared Parameter with the same name, but are from different Shared Parameter files.  If you want to remove the duplicate, you need to edit the family's parameter to reference the same Shared Parameter.  

 

BTW: Shared Parameters have common GUIDs. There is no ongoing "link" to the Shared Parameter File once the parameter has been pulled from the Shared Parameter file. In other words, the Shared Parameter File is just for creating new parameters, not managing existing parameters.  

0 Likes
Message 3 of 38

Anonymous
Not applicable
I don't understand. What do you mean parameters with the same name? These are named something different.
0 Likes
Message 4 of 38

barthbradley
Consultant
Consultant

I edited my first post to make it more understandable. Is it?

 

...are you saying that a family parameter is changing it name upon loading it into the project? I don't see how this is possible.  Are you sure?  

0 Likes
Message 5 of 38

Anonymous
Not applicable
Perhaps I'm being dense here, but are you saying that there are only GUIDs and that when you create a shared parameter it only references an already existing GUID?

Are there a limited group of GUIDs in that case? I assumed that each new shared parameter created would create it's own unique GUID.
0 Likes
Message 6 of 38

ToanDN
Consultant
Consultant
Can you zip up a family with 321Voltage parameter and share it?
0 Likes
Message 7 of 38

Anonymous
Not applicable
The shared parameter is changing its name. So I have a parameter for Maximum Overcurrent Protection named "320MaxOvercurrentProtection".

When I load the family into the project, the name changes to "Maximum Overcurrent Protection"
0 Likes
Message 8 of 38

Anonymous
Not applicable
I can in the morning when I get back to the office. It isn't only this parameter, but others as well.
0 Likes
Message 9 of 38

barthbradley
Consultant
Consultant

@Anonymous wrote:
Perhaps I'm being dense here, but are you saying that there are only GUIDs and that when you create a shared parameter it only references an already existing GUID?

Are there a limited group of GUIDs in that case? I assumed that each new shared parameter created would create it's own unique GUID.

Yes, the families are sharing GUIDs.  In other words, if you have Shared Parameter File named Alpha with a "Voltage" parameter and a Shared Parameter File  named Bravo with a "Voltage" parameter, and you create families with "Voltage" parameters from both Shared Parameter Files, you will have 2 parameters shown for "Voltage" in Project Schedules. 

0 Likes
Message 10 of 38

barthbradley
Consultant
Consultant

@Anonymous wrote:
The shared parameter is changing its name. So I have a parameter for Maximum Overcurrent Protection named "320MaxOvercurrentProtection".

When I load the family into the project, the name changes to "Maximum Overcurrent Protection"

There's something else going here.  Family parameters don't just change inexplicably when loaded into a Project. But, this is not connected to the Shared Parameter file in your Project.  

0 Likes
Message 11 of 38

Anonymous
Not applicable
This seems unlikely though. Isn't the purpose of allowing the creation of parameters so that there could be multiple instances of Voltage or any other measurement, that remain as independent data points?
0 Likes
Message 12 of 38

barthbradley
Consultant
Consultant

Not sure I understand your question, but yes, two "Voltage" Parameters could mean two entirely different things. Heck, they could be different Units as well.  Hard to know by just reading the name.  

 

...BTW, we're talking about the name of the container -- not what's in it.  

0 Likes
Message 13 of 38

Anonymous
Not applicable
That's my point actually. It seems unlikely that I've happened to create both a Voltage parameter and an MOCP parameter that share GUIDs (and datatype) with some other shared parameter file created elsewhere.
0 Likes
Message 14 of 38

barthbradley
Consultant
Consultant

@Anonymous wrote:
That's my point actually. It seems unlikely that I've happened to create both a Voltage parameter and an MOCP parameter that share GUIDs (and datatype) with some other shared parameter file created elsewhere.

 

"Voltage" parameter and "MOCP" parameter that share GUIDs?  Not possible.  

 

...I'm very interested in getting to the bottom of this. Please post the file when you can. 

 

 

0 Likes
Message 15 of 38

Anonymous
Not applicable
I mean both of them changed names to something else when put into a project. The 320MaxOvercurrentProtection became "Maximum Overcurrent Protection" and 321Voltage becomes "Voltage". Both are appropriate descriptions datatypes.
0 Likes
Message 16 of 38

barthbradley
Consultant
Consultant

Yes, I get what you're saying. I'm saying I don't believe that they are, and that something else is going on here. Hard to know for sure without seeing the file.  

0 Likes
Message 17 of 38

Corsten.Au
Advisor
Advisor

Hi

1. Step 1 : Delete Parameter from the family "Voltage"

2. Step 2 : Assign new Parameter 321Voltage in the family using " Shared Parameter "

But before all that, make sure you are updating " Shared Parameter " notepad file in

Revit project, and family...

 

once the shared parameter is loaded in the family, " your ex Voltage" , you cannot delete it as 

long as its using it.. and there is no way to rename or change it... so only way is remove it, 

and associate Family with new created parameter..

 

Cheers

Corsten
Building Designer
0 Likes
Message 18 of 38

Anonymous
Not applicable
I dont think you can delete the parameter "Voltage" as it's associated with electrical connectors.
0 Likes
Message 19 of 38

barthbradley
Consultant
Consultant

Sure you can. Whether you want to is completely up to you.  

 

...send it to me. I'll change it.  Name it something different too.  

0 Likes
Message 20 of 38

Corsten.Au
Advisor
Advisor

Hi

You cannot delete the default parameters of the families..

Ex : Width and Height from Window Family

Ex: Fire rating of walls 

etc.

 

But you can always delete Parameters which are manually created in 

1. Instance parameter

2. Type parameter

3. Share parameter..

 

For shared parameters, you can delete only if you have access to the Share parameter notepad

file, and you have rights to edit on that drive..

if the shared parameter file ( notepad ) is not available, ( ex: in cases where you downloaded

family from some website, or copied from other project / company ), then you may not have

access to the share parameter file ( notepad ) in this case you cannot edit or delete anything..

You must have local shared parameter file.. ( local, or on server )

and usually there's only one shared parameter file allowed at any given point of time for Revit..

 

best practice is to use Type or Instance parameter, and

when those two are not possible, only then shared parameters should be used..

 

Cheers

Corsten
Building Designer
0 Likes