Overview

The Auto View Renamer applies the ISO six-field naming convention (Phase_PlotSheet_Zone_ViewType_Level_) to every eligible View in the project in a single operation. Unlike 157 ISO View Namer — which renames one active View interactively — this tool runs automatically across the entire project, reading custom parameters to build each View name without manual input.

It is ideal for standardising a project at the start of production, enforcing naming conventions across a team, or cleaning up Views that were created before a naming standard was in place.

Table of Contents

• Key Features
• Requirements
• How the Naming Works
• Running the Tool
• Tips and Best Practices
• Common Use Cases
• Troubleshooting

Key Features

• Renames all eligible Views in the project in one operation — no per-view interaction required
• Uses the same ISO six-field convention as 157 ISO View Namer: Phase_PlotSheet_Zone_ViewType_Level_
• Reads Phase and Plot Sheet codes directly from custom View parameters
• Auto-detects View Type code from the Revit ViewType (Floor Plan, Section, Elevation, 3D, etc.)
• Auto-populates the Level / Location field from the View's associated level for plan Views
• Zone defaults to ZA (Zone All) for all Views
• Duplicate name detection with automatic numeric suffix to prevent conflicts
• Skips View Templates, Sheets, Schedules, Legends, and system Views — only working Views are processed
• Reports pass/fail counts on completion

Requirements

• Must be run inside a Project (not a Family document)
• The following custom View parameters must be present and populated on each View for full automation:
  • S-VW_Project Phase_T → drives the Phase code (characters 3–4 of the parameter value)
  • S-VW_Drawing Series_T → drives the Plot Sheet code (first 2 characters of the parameter value)
• If either parameter is missing or empty on a View, that View will fail to rename and be counted in the fail total
• Add S-VW_Project Phase_T and S-VW_Drawing Series_T to your project template using 108 Add Project Shared Parameters before running

How the Naming Works

The tool builds the ISO name from five components. The sixth field (Description) is not populated automatically — the trailing underscore is left in place as a placeholder, keeping the name parseable by 157 ISO View Namer for later manual completion.

Resulting name format: DD_20_ZA_PLAN_GF_

View Type Auto-Detection

Views Excluded from Processing

The tool skips all non-working Views automatically:

• View Templates
• Sheets
• Schedules and Legends
• Internal, System Browser, Project Browser views
• Cost Reports, Loads Reports, Pressure Loss Reports

Running the Tool

Launch

Find Auto View Renamer on the Bonus Tools Ribbon or use 115 Search Tools to locate it quickly.

The tool runs immediately on launch — there is no dialog. It processes all eligible Views and displays a results summary when complete.

Step 1 — Ensure Parameters Are Populated

Before running, verify that S-VW_Project Phase_T and S-VW_Drawing Series_T are filled in on all Views you want renamed. The easiest way to check is via a View schedule or the Properties palette.

If these parameters are empty or missing on a View, that View will fail and be counted in the fail total shown at the end. No Views are partially renamed — each View either fully succeeds or is skipped.

Step 2 — Run the Tool

Click Auto View Renamer on the ribbon. The tool silently processes all eligible Views. When complete, a results message displays the number of Views successfully renamed and the number that failed.

A View fails if:

• S-VW_Project Phase_T or S-VW_Drawing Series_T is missing or empty
• The assembled name causes an unexpected Revit error

Step 3 — Complete Descriptions with 157 ISO View Namer

The automated name ends with a trailing underscore where the Description field would go. Open each View individually using 157 ISO View Namer to add the Description and Title on Sheet without having to re-enter the other five fields — the tool will parse the existing ISO name and pre-fill them automatically.

Tips and Best Practices

• Run on a fresh project. The Auto View Renamer is most effective at project setup, before Views have been manually named or placed on Sheets. Running it mid-project on Views that have custom names will overwrite those names.
• Populate parameters before running. Fill in S-VW_Project Phase_T and S-VW_Drawing Series_T on all Views first — either directly in Properties or via a View Schedule. Every View missing these parameters counts as a failure.
• Use with 157 to finish descriptions. The tool intentionally leaves the Description field blank (trailing underscore). Open important Views in 157 ISO View Namer afterward to complete the name — fields 1–5 will already be populated from the auto-renamed name.
• Zone is always ZA. All Views are assigned ZA (Zone All). If your project uses zone codes like M1, S1, etc., use 157 ISO View Namer to update the Zone field per View after the bulk rename.
• Elevation and Section Views get Location TBC. The tool cannot determine compass direction automatically. After the bulk rename, update direction codes (NN, SS, EE, WW) using 157 ISO View Namer.
• Level names become the Level code. If your levels are named Level 01 rather than 01, the full level name is used in the View name. Rename project levels to short codes (GF, 01, RF) before running for cleaner results.
• Check the fail count. After running, if the fail count is non-zero, open a View Schedule showing S-VW_Project Phase_T and S-VW_Drawing Series_T to identify which Views have empty parameters, then populate them and run again.

Common Use Cases

Standardising a new project — At project start, once the View structure is set up and parameters populated, run Auto View Renamer once to apply ISO names to all Views. Follow up with 157 ISO View Namer on key Views to add Descriptions and Title on Sheet values.

Enforcing naming after a team handover — When receiving a project with inconsistently named Views, run Auto View Renamer to reset all names to a clean ISO baseline. The old names are overwritten; any Views with missing parameters are identified in the fail count for manual follow-up.

Re-stamping Views after a phase change — If the project phase changes (e.g. from SD to DD), update the S-VW_Project Phase_T parameter on all Views (via a View Schedule or Manage Parameters), then run Auto View Renamer to refresh all View names to the new phase code in one click.

Cleaning up working Views — Working and coordination Views often accumulate ad-hoc names. Setting S-VW_Project Phase_T to a working phase code (e.g. WV) and running the tool organises them into the ISO structure without manual effort.

Combined workflow with 157 — Use Auto View Renamer as the foundation pass to get all five fields in place quickly, then use 157 ISO View Namer for the detail work: adding Descriptions, setting Title on Sheet, assigning View Templates, and correcting zone or location codes where needed.

Troubleshooting

High fail count on first run The most common cause is missing or empty S-VW_Project Phase_T or S-VW_Drawing Series_T parameters. Create a View Schedule with both parameters as columns to quickly identify which Views are not populated. Populate the missing values and run the tool again — successfully renamed Views will simply be renamed again with the same result; failed Views will now succeed.

Parameters exist but Views still fail Check that the parameters are added as instance parameters on the View category, not type parameters. The tool reads them with LookupParameter() which operates on the View instance. Also confirm the parameter values contain enough characters — Phase requires at least 5 characters (to extract characters at index 3–4), and Drawing Series requires at least 2 characters (to extract the first 2).

Views renamed with Location TBC in the Level field This happens for Elevation and Section Views, which have no associated level in Revit. The tool cannot determine compass direction automatically. Use 157 ISO View Namer on each elevation/section View to replace Location TBC with the correct directional code (NN, SS, EE, WW, etc.).

Level field shows the full level name instead of a short code The tool reads the actual Revit level name. If levels are named Level 01 or Ground Floor, those full names appear in the View name. Rename project levels to short codes in the project settings before running the tool, or correct individual View names using 157 ISO View Namer.

Tool won't run in a Family document The Auto View Renamer only operates in project files. If you launch it while a Family is open, the tool will display a warning and exit without making changes.

Duplicate names getting numeric suffixes When two Views of the same type are on the same level with the same phase and plot sheet, the assembled names will be identical. The tool resolves this by appending 0, 1, 2, etc. to make each name unique. If this is unexpected, check whether multiple Views of the same type exist on the same level — use 157 ISO View Namer afterward to add distinct Description text to differentiate them properly.

View Templates, Schedules, or Sheets were renamed unexpectedly This should not occur — the tool explicitly excludes all non-working View types. If it does occur, verify you are running the latest version of Bonus Tools.