Standard architectural documentation convention dictates that all notes should be in uppercase. When working in Revit, if a team member hasn’t followed this convention, it can be a significant task to fix. Especially if you have hundreds of views and sheets. Rather than updating these manually, it is possible to use a plug-in such as BIMlink. From there, they can be modified in Excel using the UPPER () function, before being imported back into Revit. This is somewhat tedious and can be further expedited with the use of Dynamo.
As part of the Parametric Monkey Dynamo package, there are three custom nodes: ‘View.NameToUppercase’, ‘Sheet.NameToUppercase’, and ‘Schdule.NameToUppercase’.
The ‘View.NameToUppercase’ uses the ‘View.IsViewTemplate’ node from the Clockwork package. It will update both the view name and “Title on Sheet” parameter.
The ‘Sheet.NameToUppercase’ will update both the sheet name and sheet number parameters.
The ‘Schedule.NameToUppercase’ is a little more complicated because we need to exclude the revision schedule, which is nested into title block families. Once this is done, it will update the view name.
Despite being super simple, these custom nodes are highly effective and may save you loads of time.
Manish Paul Simon
I got a null value when trying the View name renaming. So I used the Object.IsNull node and then filtered by boolean mask to remove any nulls.
What was the point of the Clockwork Node View.IsViewTemplate+ in renaming views? Didn’t quite understand the use.
Can you post a link to an image that shows the problem. Without it, it is pretty hard to understand what is going on.
When the graph is collecting all elements of category (views), this returns view templates as well so I am simply filtering them out of the renaming process.