Rule engine
- OR between groups, AND inside each condition group
- Each rule writes to its own target parameter
- Token formulas concatenating several source parameters
- Supports string, integer, double, yes/no and ElementId storage
Fill parameters in bulk from a rule set: each rule writes to its own target parameter, with token formulas and a scope limited to a view or a selection.
Revit's IF() formula only runs inside the Family Editor, on that family's own parameters — there is no built-in way to write a conditional value across hundreds of elements spanning several categories in a project, and that job falls straight onto whoever on the team can script Dynamo.
With no project-wide conditional formula, the BIM team has to build the Dynamo nodes, test them, then maintain the graph every time a family or parameter gets renamed.
Building a Mark from Level + Category + a sequence number, for instance — Revit has no built-in string-join formula, so automating it means a Dynamo String.Join node, or typing every row by hand.
A Dynamo script writes straight to the model when it runs — knowing the row count in advance means bolting on a Watch node yourself, otherwise you're gambling with the whole model.
A Dynamo script is wired to that specific file's family and parameter names — move it to another project, or rename one element, and the graph throws errors that need rebuilding almost from scratch.
On the App Store, Parameters Package ($5/month) has a tool for joining several text parameters into one — close to Fill Parameter's token-formula idea — but it only works with Text-type values, has no AND/OR conditions to target the right elements, and tops out at Revit 2022. Beyond that narrow slice, conditional parameter filling in Revit is still Dynamo's job. Fill Parameter packages that rule engine into a no-code interface:
The interface is matched to the tool window running in Revit.
See every family and type in the project: what is used, what is not, renamed and reloaded in batches.
Create, bind and remove shared parameters by category; find missing parameters before quantity take-off.
Map and convert values between any two parameters using rules you define.