Soo many parameters in properties palette

[dkarnes345]

Hi,

I am seeing a somewhat random logic to how instance parameters are linked to mechanical equipment, many of which may be project parameters added unintentionally.  Why are things like SEER, COP, Total Cooling Capacity becoming assigned to certain families (and visible in the dialogue) even though they are not part of the family?  Is there a way to simplify and reduce the number of these fields which never apply to certain families e.g. pumps and COP?  When does a parameter turn into a project parameter though it started as a shared parameter prior to loading the family?  Naming convention issue?

Thanks much!

Dan

[RobDraw]

Yeah, sorry, not opening a .docx. An image would be better suited here. I would like to see what you are showing in case my guess is wrong.

It's probably a lot harder to sort out parameter issues after the fact, than it is to prevent them from getting out of control. Start with a good template and vet any and all content for non-standard parameters before it goes into the project.

[ennujozlagam]

@dkarnes345 hello, i'm not sure if your .docx file attached is from a family parameters? or you can try to go to manage > Project parameters > remove from there and see if helps. thanks

[Anonymous]

may be project parameters added unintentionally.

This is it.  At some point someone added a bunch of project parameters to your template and assigned them to all families of the category Mechanical Equipment.  They won't hurt anything, they're just annoying.

[dkarnes345]

Thanks all for the quick turnaround!! - Agreed.  I did a test with our clean project template, and the properties window seems fine.  There is definitely something related to what is loaded in that appears to be the issue.  COP, SEER, Requires Electrical Connection... all seem to be built-in parameters from Revit.  If any of these are named identically as a shared parameter, would that cause them to be assigned to all mechanical equipment?  The group seems in concurrence that the properties window can be controlled (only showing what is applicable to the family and schedules) to what is visible then thru good content and parameter control.  That was the heart of the question. 

[dkarnes345]

My hunch is not to do with the template.  These seem to be tacking onto to M Eqpt while Revit is trying to reconcile what the parameters are for.  It may be connected to if the shared parameter file (opened/linked) matched those parameters the family thought were shared.  There seems to be issues with not having all shared parameters being used in a single common file perhaps. Some shared parameters (became both shared and project automatically), may not have existed in the shared parameter file I was "connected to."

[dkarnes345]

Sorry to keep this string so long, but that was the challenge.  Once some of these parameters had become project parameters, deleting them also deletes the shared parameter.  So however these shared ones turned into project types, now causes that field to muddy the properties for all M eqpt, making it less usable. We are forced to do this from a schedule when families are broken, but this project example is clean. No forcing parameters into schedules as of yet.