Domain Data Filters
Structural filters answer what something is — its type, category, position in the hierarchy.
Domain data filters answer what something means — its classification, coding, or business intent. This data drives scope decisions at a higher level: not "give me all doors" but "give me all elements classified under assembly code 32.31".
What you will learn
- How to filter by Assembly Code using an explicit list
- How to use regex to match structured Assembly Code patterns
- How to correctly filter
FamilyInstanceobjects by category via theirFamilySymbol - How to chain Family → FamilySymbol → FamilyInstance into a single production-grade filter
Pages in this section
Filter by Assembly Code
How to scope a rule to specific Assembly Codes using an inclusion list. Explains why Assembly Code lives on the FamilySymbol, not the instance.
Filter by Assembly Code — Regex
How to use a regular expression to match structured Assembly Code patterns. Includes a real-world example and guidance on testing regex with regex101.com.
Filter FamilyInstances by Category via Symbol
The correct two-step approach for filtering placed elements by category: first filter the symbols, then the instances. Explains why direct category filtering on instances is fragile.
Chain — Family, Symbol, Instance
A complete three-level filter chain combining naming conventions, editability, category, and classification into one rule. The production pattern to build towards.
Prerequisites
You should already understand:
- Two-step filtering — see Two-Step Filtering
- Why category filtering belongs on the
FamilySymbol— see Revit Object Hierarchy - The
inoperator and inclusion lists — see Filter by Category — Inclusion List