Hi all,
I am trying to menage as best as i can Shared parameters. I would like to have list of shared parameter so named "Company Prefix_Description"
I have noticed that same shared parameter can be used in different categories . E.g. XX_Height can be used for column height, foudantion height and so on.
So my question is : it s better prepare a bunch of shared parameter for main dimentions and add in different category families, or prepare shered parameter per each category e.g. XX_Height_Column, XX_Height_Beam and so on? Or its better prepare shered parameter so named XX_1,XX_2... XX_n?
Thanks for any tip
Here I am adding one link for best practice on Parameter naming convention.
https://www.caddmicrosystems.com/blog/2017/07/revitparameter-namingtips/
Hi
There are some good tips, but quite far for what I am in need. Thanks for the effort
@XXalessio.amodioXX wrote:
Hi all,
I am trying to menage as best as i can Shared parameters. I would like to have list of shared parameter so named "Company Prefix_Description"
I have noticed that same shared parameter can be used in different categories . E.g. XX_Height can be used for column height, foudantion height and so on.
So my question is : it s better prepare a bunch of shared parameter for main dimensions and add in different category families, or prepare shered parameter per each category e.g. XX_Height_Column, XX_Height_Beam and so on? Or its better prepare shered parameter so named XX_1,XX_2... XX_n?
Thanks for any tip
My question would be why are you naming Shared parameters (or any parameter for that matter) with Company Extensions? What's the purpose?
@XXalessio.amodioXX wrote:So my question is : it s better prepare a bunch of shared parameter for main dimentions and add in different category families, or prepare shered parameter per each category e.g. XX_Height_Column, XX_Height_Beam and so on? Or its better prepare shered parameter so named XX_1,XX_2... XX_n?
May I point out that the OOTB Revit has a "bunch" of in-built Shared Parameters that are the same name across Categories (i.e. Window Family "Width", Door Family "Width", etc.). Seems to work pretty well. No conflicts reported.
Hi
Main idea is to prepare costum firm family with all shared parameter in order to scheduling easier by presetted schedule in tamplate
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.