Thursday, 12 February 2015

Translating shared parameters

When you open a Revit shared Parameter file it says:
# This is a Revit shared parameter file.
# Do not edit manually.

I don't know about you guys but I always feel like trying to see what you can edit anyways. These sort of statements always have this sort of effect on me.
BIG DISCLAIMER do not edit shared parameters that have been used in projects or families! If you do any edits based upon what you read here. It is your OWN responsibility! Next BIG DISCLAIMER this was all done with Revit 2015 R6

Names
The most interesting thing about editing this file for me is: Will it work if I translate the parameter names to other languages. A very small test showed me that these parameters, I tried, worked out. Be aware I have only tested these. Just because these work does not mean others will work!

I did the following:
I created a new shared parameter file with 4 shared parameters with Dutch names. I created a family and I used these parameters. I loaded the family into a project and I created a schedule. Nothing fancy it works, of course.

Next I copied the sp file and renamed it to something else. I edited the sp file and I changed the names of the shared parameters to an english equivalent. Next I created a new family with these english shared parameters. What happens if both these families get into a project? It depends who was loaded first. Revit will use the names of the parameter which came first. 

It get's a little bit more interesting if you use linked files. For example a Dutch architect and an English engineer. 
If you link the architect file into the engineers file it's the other way around.
This would make you think it works. But I have heard people with different stories. It's worth further investigation.

Other edits I tried.

Moving Parameters to another group
A simple edit that so far I have been able to get away with was moving parameters from group to group. 

Changing the parameter type:
It is possible to change the type of a parameter. But I recommend you don't! Because the following below is something you will see in your project very soon!

The shared parameter '4d3f4a8c-357e-4af0-a8f9-de40e87e2f6d' cannot be added with name 'diepte' and type 'Text' because it conflicts with the existing name 'diepte' and type 'Length'.

VISIBLE:
If you change this value from 1 to 0 it will have the effect whether the parameter is visible in the project. Except if you have used this parameter already in the project. It will retain it's setting from the first family.

USERMODIFIABLE:
If you change this value from 1 to 0 it will have the effect whether the parameter is changeable in the project. Except if you have used this parameter already in the project. It will retain it's setting from the first family.

Important to remember if the parameter has already been used in a project than the changes described above will have no effect or will render the family you are adding later useless. You might have noticed I haven't edited the GUID. This will definitely break it.



Google+ Badge