Parameter Formula Propagator
PremiumGenerate parameter values from template patterns and sequential numbering. · Explore the live interface below - every control works exactly as it does inside Revit®.
Architecture
Structure
Steel
Precast
Systems
Insert
Annotate
Analyze
Massing & Site
Collaborate
View
Manage
Add-Ins
NexionTools
Select
Highlight
Rooms
Parameters
Sheets & Views
Data
Manage
QC
Test it Live - exactly as if you are in Revit
Loading interactive demo…
Get Started in Minutes
Four simple steps to bring Parameter Formula Propagator directly into your Revit® environment.
1
Create Account
Sign up for a free NexionTools account - no credit card required.
2
Download Installer
One installer, 52 professional Revit® tools. Under 15 MB.
3
Open Revit
Parameter Formula Propagator appears in your ribbon automatically - ready to use.
4
Activate License
Enter your Premium key to unlock full features.
Ecosystem · Parameters
Try NexionTools completely free.
Get full access to all 40 premium Revit® plugins. No credit card required.
Why Parameter Formula Propagator exists
Half the data in a model follows a pattern that lives in someone's head. Door marks are the level plus a running number. Equipment tags are a discipline prefix, a level, and a sequence. It is completely predictable, and it still gets typed in by hand, one element at a time, with the inevitable duplicate at element forty that nobody notices until the schedule is issued.
How Parameter Formula Propagator works
Pick a category and the parameter you want to write to - the list offers writable parameters with the common ones first.
Start from a quick template or type your own shorthand. Something like D-LEVEL-#3 expands to a full expression that numbers sequentially within each level, and the dialog shows you the expanded form so the shorthand is never a black box.
Build more specific patterns from token chips grouped by what they refer to: identity, the space an element sits in, the element itself, the project, and separators.
Preview before writing. You get counts for what will be filled, what will be updated, what is already correct, and - importantly - how many duplicates the pattern would produce.
Apply, and the results are written in one transaction - one undo entry for the whole run. Change the formula after previewing and it warns you the preview is stale rather than applying something you did not look at.
Before
The naming convention is documented in a PDF and applied by hand, so it drifts as soon as the project gets busy.
After
The convention is a pattern you run, applied the same way on element four hundred as on element one, with duplicates caught before they reach a schedule.
When to reach for it
- Door and window marks derived from the level and a sequence.
- Equipment tags built from discipline, level and a running number.
- Re-applying a naming standard to a model that was started without one.
What it does not do
- It generates values from patterns and writes them in. It is not a Revit family formula and does not recalculate on its own when the model changes.
- It writes to text and whole-number parameters. Length, area and family-type parameters are skipped - the pattern produces a string, and those do not take one.
- Tokens that read the space an element sits in need placed, named rooms to read from.
- The scope is every instance of the category in the project. There is no view filter and no selection filter.
- The preview table shows the first five hundred rows and tells you so; the counts and the apply itself cover every element.
- On a non-English Revit the category-prefix shorthand falls back to the first four letters of the localised category name, so Portes becomes PORT rather than D.
- On a workshared model, elements owned by other users are checked out where possible; those that stay locked are marked, skipped and counted as failures.
- It will not invent a convention for you. Deciding the pattern is still your job.
Questions
- How is this different from a formula inside a Revit family?
- A family formula is calculated by Revit from other parameters in that family and recalculates on its own. This generates values in the project from a naming pattern - including things a family formula has no access to, like the level or room an element sits in - and writes them into the parameter as ordinary values.
- Can it number elements sequentially?
- Yes - the shorthand for a sequence restarts the counter per level rather than running straight through, so a counter sits inside a larger naming convention instead of being a separate pass.
- What if the pattern produces duplicate values?
- The preview counts them before you apply, and rows that would produce a duplicate are left alone rather than written - so a pattern that runs out of unique values leaves the remainder carrying their old values, with the count shown. If uniqueness across a whole category is the requirement rather than a side effect, Unique Numbering is the tool aimed specifically at that.
- Can I get the result out for checking before applying it?
- Yes - the preview exports to CSV or Excel, so a naming change can be reviewed by someone else before it touches the model.