Finding Unused Opening GPs¶
Use Find Unused Opening GPs to identify Global Parameters whose names match Flow's opening-related naming patterns but for which the current scan detects no association.
You can review a name preview and either leave the candidates unchanged or delete the complete candidate set.
Ribbon: Flow → Content → Parameters Manager
Before You Start¶
Use this workflow only after reviewing the project and confirming that obsolete opening GPs should be removed.
Type-only associations may not be detected
The current unused-GP scan checks parameters on non-type elements. A GP used only through a type-parameter association may be classified as unused and offered for deletion.
Review unfamiliar candidates with Review Associations or Revit's native Global Parameters tools before confirming deletion.
Find Unused Opening GPs¶
- Open Parameters Manager.
- Expand Maintenance.
- Select Find Unused Opening GPs.
- Wait while Flow scans the current project.
- Review the candidate count and name preview.
If no candidates are found, Flow reports:
No unused opening global parameters were found.
No changes are made.
Review the Confirmation¶
When candidates are found, Flow displays:
- Total number of apparently unused opening GPs
- A preview of up to 30 GP names
- The number of additional candidates when more than 30 are found
- Yes and No choices
Candidates are ordered alphabetically in the preview.
The list is not individually selectable
The confirmation is a preview, not a checklist. Yes deletes the complete candidate set found by the cleanup scan. You cannot exclude individual names in this window.
Choose No if any candidate requires further investigation.
Which Global Parameters Are Considered¶
Flow limits the search to GP names beginning with one of its opening-related patterns, including:
Window Head HeightX-Window Head HeightZero Window Sill HeightArchitraveGlassThicknessExt_SillExt_TrimExt SillExt TrimExterior SillExterior TrimFrame SetbackJamb LinerWindow GlazingWindow HardwareWindow Type
The name check is case-insensitive and uses the beginning of the GP name. It can therefore include level-specific and wall-type-specific names that continue after the recognised prefix.
This command is not a general cleanup of every unused Global Parameter in the project.
Protected Global Parameters¶
These exact names are protected and are not offered for deletion:
Window Head HeightX-Window Head HeightZero Window Sill Height
The protection is case-insensitive.
Names that merely begin with one of those protected names can still be candidates. For example, a level-specific Window Head Height GP is not protected solely because it shares the prefix.
Delete the Candidates¶
If you have reviewed the candidate set and want to proceed:
- Select Yes.
- Flow runs the unused-GP check again when the Revit cleanup event executes.
- Each current candidate is deleted inside one Revit transaction.
- Review the completion result.
- The Opening GP Dashboard refreshes automatically.
The completion result reports:
| Result | Meaning |
|---|---|
| Found | Number of candidates found by the deletion-time scan. |
| Deleted | GPs successfully deleted. |
| Failed | Candidates that could not be deleted. |
An individual failure does not prevent other candidates from being deleted. Successfully deleted GPs are committed even when another deletion fails.
Expected Result¶
After confirmed cleanup:
- Successfully deleted candidate GPs no longer exist in the project
- Protected exact-name GPs remain
- Failed candidates remain
- The dashboard is rescanned automatically
Deleting a GP is different from removing an association. This workflow removes the GP element itself.
Leave the Candidates Unchanged¶
Select No in the confirmation.
The workflow closes without deleting anything. You can then:
- Use Review Associations on representative window instances.
- Review relevant window types in Revit.
- Use Revit's native Global Parameters editor.
- Run the cleanup again after confirming the candidate set.
If an Expected GP Appears in the List¶
Do not confirm deletion.
Check whether:
- The GP is associated only with a type parameter.
- Its intended family instances or types are absent from the current project.
- Its association was removed unintentionally.
- It is a level-specific or wall-type-specific GP awaiting use.
- Its name matches an opening prefix even though it serves another purpose.
Current Limitations¶
- Type-only associations may not be detected.
- Candidate scope is determined partly by GP-name prefixes.
- The preview does not allow individual candidates to be selected or excluded.
- Confirming deletion processes the complete candidate set found at execution time.
- Individual failures are counted but do not roll back successful deletions.
- The command does not find unrelated unused project GPs.