Simple dynamo script for title sheet

[yes_and_no]

Our title sheet family has improved over time with revision number like v1, v2 as suffit. (Right now we have v64).

For project file, we still use past similar project and save as new one. (I guess everyone still doing that), and that of course bears the old title sheet family.

The title sheet families has about 5 sub families tailored for cover sheet, detail, plans, etc.

• What bothers me is swapping them to newest version. The "select all in project" and swap all never work perfectly, I just don't know why.

I wish some one can share a dynamic script or similar method to automate this routine task, knowing the only difference between these are only the suffix v# in their names.

Thx.

[RLY_15]

The complexity of a dynamo script is usually in workflow-specific items.

You've mentioned that you have a Cover Sheet type, a Detail type, a Plan type, etc.... is that true for all 64 versions, and is the naming convention the same

This is a (very) rough graph that would let you manually create a list of different family types (you would choose all of your v64 Family Types), and then set up search terms for each type.

Assuming that every family is structured so that you have a 'Cover Sheet' type, a 'Detail' Type, etc. with consistent and nonoverlapping terms, you can use the String.Contains node to organize every titleblock in the project so that it updates to the latest version.

If you have a titleblock that does NOT match any of the strings, the List.Indexof Node will return a -1 instead of a proper number. You'll then need to inspect those titleblocks to figure out why and correct as needed.

[yes_and_no]

Thx.

The sub family has the same name convention.

Only the host family has version number.

Can you repost a better resolution image, or perhaps into two shots. I can't read it.

• Thx again