How to Use StructuralType Enumeration in Dynamo (Beyond Category Filtering)

Hi everyone,

I understand the value of the StructuralType enumeration when scripting, but I’m trying to better understand how the members of RevitNodes.Revit.Elements.StructuralType are intended to be used within a Dynamo graph.

Specifically, is there a practical use case where these values help filter or identify elements such as structural beams? I’m not referring to filtering by category — rather, I’m looking for how the StructuralType node itself is meant to function in a graph, since it doesn’t behave like a category filter.

If anyone has an example or explanation of its practical use, I’d appreciate it.

in terms of nodes, it depends on how the zero-touch developer intends to adapt the node when using it as an input—whether it is for filtering purposes or for creating instances. generally speaking, whether in node graph or scripting, i often see this parameter used as an input for creating family instances. for example, suppose you have a custom family that represents a structural footing, or an uniquely shaped opening (which i see them all the time in many jobs). even if the family symbol geometry is placed under a category that is not structurally related—such as generic models—the instance eventually still gets assigned to a structural type when it is created.

in that case, you can still use ElementStructuraltypeFilter (a quick filter) to efficiently retrieve those elements. to some extent, this approach could be more robust and maintainable than filtering based on things like element name, some parameter added solely for identification.

also take a look at the post below. i think these nodes have some issue where they don’t match the underlying enum.

Split Beam At Parameter Points - Developers - Dynamo

1 Like