Built-in parameters that exist on specific family categories should be available for reference within the family editor. In a trapeze hanger family, rod lengths should be able to calculate directly from elevation data, but the elevation parameter is not accessible. This forces users to duplicate built-in values into custom parameters, creating redundancy and potential data mismatch. If a parameter exists, it should be usable in family formulas. Unify parameter identity and remove the distinction between shared and non-shared parameters. Revit could: Give every parameter a GUID automatically Store identity internally (not a text file) Allow any parameter to be: Tagged Scheduled Exported Provide a Parameter Manager UI Allow GUID migration and merging Keep backward compatibility Shared parameters cannot have their tool tips or descriptions edited after creation, and moving parameter storage internally would allow metadata to be updated without breaking parameter identity. Revit formulas are overly restrictive and lack many basic features found in modern parametric or scripting environments. Users cannot perform conditional logic based on text parameters, nor can they concatenate values to form meaningful strings. For example, creating a build ID like SU-10' from a strut type and length parameter is not possible using native formulas, even though this is a common and practical workflow. These limitations force unnecessary manual input or reliance on Dynamo and external tools for simple logic. Revit formulas should support basic string comparison, concatenation, and more flexible conditional logic. System families cannot accept custom parameters, which creates major limitations for scheduling and data consistency. For example, conduit does not allow user-defined parameters, making it impossible to map its built-in length to a common parameter shared with conduit fittings. As a result, schedules cannot aggregate conduit and fitting lengths together. Allowing users to add non-geometric parameters to system families—solely for data forwarding and scheduling—would resolve this without compromising system family integrity. Revit lacks a built-in mechanism to automatically keep dependent parameters in sync when elements are moved or modified. In many workflows, parameters such as Area, Level, Zone, or Location should update automatically when an element changes position. For example, if a trapeze hanger is moved to a new area, its area-related parameters should update immediately without requiring a manual script or external tool to be run. Add-ins like Evolve’s parameter sync demonstrate the value of this capability, but this functionality should be native to Revit. A built-in parameter synchronization framework would allow users to define rules or scripts that specify which parameters should update based on model changes, improving data reliability and eliminating manual coordination steps.
Show More