a week ago
Schedules in Archicad can be configured to display various element types and their properties. However, when working with complex elements like Curtain Walls, Railings, or Stairs, sub-components may appear alongside primary elements, creating cluttered documentation. This article demonstrates how to use an expression-based Property to filter out sub-elements from schedules, resulting in cleaner and more focused project documentation.
When schedules are generated based on Element Type, sub-elements are automatically listed alongside their parent elements.
These sub-elements include:
Curtain Wall accessories, frames, and panels
Railing posts and rails
Stair risers, treads, and structure components
Sub-elements typically display with their host element name in parentheses (e.g., "Panel (Curtain wall)" or "Rail (Railing)"). In many documentation scenarios, these sub-elements are not relevant and make schedules difficult to read and manage.
Open Property Manager.
Create a new Property (e.g., "Sub-element").
Set the Property type to Expression.
Insert the following expression:
IF ( OR ( CONTAINS ( "(Railing)"; {Property:General Parameters/Element Type} ); CONTAINS ( "(Curtain wall)"; {Property:General Parameters/Element Type} ) ); "Y"; "N" )
The keywords "(Railing)" and "(Curtain wall)" identify sub-elements by detecting their host element name in parentheses. Additional element types can be added by including more CONTAINS functions within the OR statement.
Apply the Property as a schedule criterion
Open the Scheme Settings for the desired schedule.
Navigate to the Criteria tab.
Add the newly created Property as a criterion.
Set the filter to exclude elements where the Property value equals "Y" (or include only "N" values).
When placing or editing elements, the expression automatically evaluates whether an element is a sub-element. Elements identified as sub-elements receive the value "Y", while primary elements show "N". The schedule criteria filters out all elements marked as "Y".
Schedules display only relevant primary elements, while sub-elements are automatically excluded based on the expression criteria. This approach eliminates manual filtering and ensures consistent documentation across the project. The filtering remains dynamic—if additional complex elements are added to the project, the expression can be extended to accommodate new sub-element types.
These techniques were originally shared by Community member @kmitotk. If you’d like to explore the original discussion, click here to read the full thread!
This article is part of the ‘Tip of the Month’ series on Graphisoft Insights, highlighting valuable community-driven solutions for modeling challenges. Try these methods in your next project and experience the difference in model quality and efficiency.