Revit will not rename a shared parameter — its identity is a GUID and the name is set the day it is born. So wrong names outlive projects, standards drift, and nobody dares touch the file. Rosetta renames shared parameters safely: same GUIDs, every value kept, a backup before anything moves.
A shared parameter's name is written into the SPF, bound into models, quoted in schedules and view filters. Revit offers no rename — only a new parameter, and a hole where the data was.
One grid, one mapping — and between you and the write: live validation that blocks errors, a dry-run report you can read first, and a backup that must exist before the file is touched.
Reload reads the active model and the shared parameter file together: bound shared parameters, project parameters, and the definitions that live only in the file. Kind, data type, group, scope — and an In use column that has already done the detective work. Filter by kind, search by name, group, category or data type.
| Current name | Kind | New name | Type | Group | Scope | In use | Status |
|---|---|---|---|---|---|---|---|
| FireRating | Shared | Text | Identity | Instance | 1 sched · 1 filter · 1 colour | ||
| AcousticRating | Shared | Text | Identity | Instance | 1 sched | ||
| Room Occupancy | Shared | Integer | Data | Instance | 1 sched · 1 colour | ||
| Sheet Series | Project | Text | Data | Instance | 1 sched |
Rosetta scans every schedule field — combined columns and embedded schedules included — every view-filter rule, however nested, and every colour-fill scheme. In use is not a guess; it is the list of exactly what breaks if you get this wrong. Lens reads the same audit: press Run on an element's Rosetta card and it says which of its parameters are shared, and where they are used.
| Current name | Kind | New name | Type | Group | Scope | In use | Status |
|---|---|---|---|---|---|---|---|
| FireRating | Shared | Text | Identity | Instance | 1 sched · 1 filter · 1 colour |
Each new name is checked live against Revit's naming rules, the whole file's final names — collisions after the rename, not before — and your office convention if you switch BIMIO naming on. Errors go red and block; warnings explain themselves. Or round-trip the mapping through Excel: Template… exports the file's parameters, a colleague fills the NewName column, Import… brings it back — the GUID, not the spelling, is the key.
| GUID | OldName | NewName | Group | Notes | |
|---|---|---|---|---|---|
| 2 | a1f4…9c2e | FireRating | BIMIO_FireRating | Identity | |
| 3 | 77b0…4d11 | Room Occupancy | BIMIO_Occupancy | Data | |
| 4 | c3e8…120f | AcousticRating | Identity | keep as is |
Dry-run touches nothing. It counts the elements holding a value for each rename, lists the schedules and view filters that depend on it, and hands you a self-contained report you can read, save or send — before you commit to anything.
| Old name | New name | Elements | Schedules | View filters | Notes |
|---|---|---|---|---|---|
| FireRating | BIMIO_FireRating | 214 | Door Schedule — L01 | FIRE-60 | |
| Room Occupancy | BIMIO_Occupancy | 63 | Room Schedule | ||
| DoorHardwareSet | BIMIO_HardwareSet | 0 | Not bound in this project (SPF-only rename). |
Rename SPF rewrites the shared parameter file — GUIDs untouched, a timestamped .bak saved beside it first; if the backup cannot be written, neither can the file. Rename in model goes further: it snapshots every value, rebinds each parameter under its new name and restores the values in one undoable transaction — re-pointing dependent schedules and view filters as it goes. Anything it cannot rebuild faithfully it refuses or skips, and says so. One failure and the whole gesture rolls back. Every operation lands in a history you can browse, with the backups a click away.
New… authors a shared parameter and binds it in one gesture. Bind… puts a batch of file definitions onto the model in one transaction. Convert… changes a parameter's kind wherever the API honestly allows — family to shared with every type value and formula verified afterwards, and a rollback if anything would be lost. Sweep… converges a whole folder of families on the file's standard, dry-run first and a backup per file. And Fill… stamps what Revit knows but never hands you as a parameter — coordinates, the rooms either side of a door, phases, sizes — into real parameters, counted and confirmed before a single write.
Rosetta ships on the Data panel of the BIMIO tab. Open your model, read the audit, and rename what has been misspelt for years — with a backup, a dry-run and a way back. Revit 2024–2027, full trial, no card.