The Add Shared Parameters extension automates the process of adding and managing shared parameters in Revit models. Shared parameters are custom data fields that maintain consistency across multiple projects and can be used in schedules, tags, and filters. This extension allows you to add multiple shared parameters at once, update existing parameters, merge duplicates, and automatically create schedules with the selected parameters.
This extension is particularly useful when standardizing project parameters across teams, implementing company standards, or migrating parameter definitions to new projects.
Shared Parameter file: Path to the shared parameter text file (.txt) that contains the parameter definitions. You can browse to select the file. The extension supports environment variables in the path (e.g., %USERPROFILE%\Documents\SharedParams.txt).
Parameters to insert: List of parameter names from the shared parameter file that you want to add to the model. Select one or more parameters from the list. The list is automatically populated from the shared parameter file you specified.
Parameter group: The group under which the parameters will be organized in Revit's parameter dialogs (e.g., Identity Data, Dimensions, Construction). This helps organize parameters logically. Default is "Identity Data".
Change Parameter group: When enabled (default: Yes), the extension will update the parameter group for parameters that already exist in the model to match your selected group. If disabled, existing parameters keep their current group assignment.
Binding type: Determines whether parameters are attached to type or instance level:
Default is "Instance".
Change binding type: When enabled (default: No), the extension will change the binding type of existing parameters to match your selection. This requires deleting and reinserting the parameter, which will preserve existing values for elements in the specified categories.
Groups: Controls how parameter values behave across group instances:
Categories: List of Revit categories (e.g., Walls, Doors, Windows) that the parameters should be added to. Selected categories will have access to these parameters. If not specified when adding new parameters, the extension will fail.
Reset categories: When enabled (default: No), replaces all category assignments on existing parameters with only the categories you specified. Use with caution as this removes the parameter from any categories not in your list.
Remove categories: List of specific categories to remove from existing parameter bindings. This allows you to selectively remove parameters from certain categories while keeping them on others.
Replace parameter: Options to handle parameter definition changes in the shared parameter file:
Selecting either option triggers deletion and reinsertion of the parameter with value preservation for elements in the specified categories.
Merge parameters: When enabled (default: No), automatically merges duplicate parameters with the same name into a single parameter. Values from all duplicates are preserved by transferring them to the merged parameter. This is useful for cleaning up models with parameter conflicts.
Reinsert parameter: When enabled (default: No), forces deletion and reinsertion of the parameter even if no changes are detected. Use this when you've modified other aspects of the parameter definition in the shared parameter file (like GUID) that aren't automatically detected.
Schedule name: Optional. If provided, the extension will automatically create a new schedule containing all the parameters you added. The schedule will include all categories specified in the Categories setting. Leave blank to skip schedule creation.
The Add Shared Parameters extension performs the following operations:
Prerequisites:
Configuration:
Execution:
Verification:
Q: When should I use Instance vs Type binding?
Q: What happens to existing parameter values when I change the binding type or parameter name?
Q: Can I add parameters to schedules in other categories beyond the ones I selected?
Q: What does "Varies across groups" mean?
Q: What happens if I select "Replace parameter" for both Name and Type?
Q: Can I run this extension on multiple models at once?
Q: Why are some of my values not being restored after a parameter update?
Version 0.1.3 - Current
Version 0.1.2
This documentation was generated based on the extension's code structure.