1. Describe the automation
Open your project, connect Revit and start a new chat. Explain the scope and naming choices you need:Create an automation to rename views selected in Revit’s Project Browser. If nothing is selected, use the active view. Exclude sheets, view templates and linked views. Let me build names using the existing name, level, view type, prefix, suffix and sequence number. Add controls for finding and replacing text, numbering and duplicate names. Apply the names when I click Run. Preserve unrelated views and report any names that cannot be changed.Start with a small set of views and one naming rule. Extend the automation after checking that first result.
2. Define the naming pattern
Ask for a Naming pattern field with these placeholders:
In the test shown below,
{prefix} - {name} with prefix GA changes DOCS - Naming 01 to GA - DOCS - Naming 01. The same rule is applied to three selected sample views.
For a numbered drawing set, use {prefix} - {level} - {type} - {seq}. With prefix A, a level named 01 and two-digit numbering, a proposed name could be A - 01 - Floor Plan - 01.
Ask the automation to omit empty sections separated by - and flag invalid names. If the pattern requires a level that a view does not have, it should skip that view and report why.
3. Add the controls
Ask Ideatura to expose the settings you will change between runs:Add Prefix, Suffix, Find, Replace, First number and Number digits. For duplicate names, offer Skip or Add numbered suffix. Default to numbering from 1 with two digits, Skip duplicates.Specify that Find should match exact, case-sensitive text within the existing name. Leaving Replace blank removes that text. These controls affect the
{name} part of the pattern.
Ask to number views in natural order by their existing names: View 2 comes before View 10. Skipped views may leave gaps in the sequence.
4. Select views and run
Save your project. Select two or three views in Revit’s Project Browser, check the naming inputs, then select Run. This automation takes its scope from the Revit selection; it does not need a separate view-selector field. With nothing selected, it uses the active view. If the selection contains no eligible views, it stops rather than switching to another scope. Review the changed names and any skipped views. Ask for up to three before-and-after examples in the report, so you can check a small test without a long list. For conflicts, Skip leaves the affected view unchanged. Add numbered suffix appends(2), (3) and so on.
5. Inspect the result
The test renamed three selected views. Their new names are visible in the Project Browser below; their sheet titles match the original plans. Open your renamed views and check that their names match your drawing convention. Check the resulting names in the Project Browser against the naming pattern. Ask the automation to read the names back after applying them and report any rename that could not be completed.
6. Save and reuse
Once the result matches your convention, save the automation with a clear name and description. Save the Revit project separately. Check the selection and pattern before each subsequent run. A pattern containing{name} uses the current name, so applying the same prefix or suffix again can repeat it.
This example tests adding a prefix. Test find-and-replace, numbering and duplicate-name handling on a small set before using those rules across a drawing package.