View Filters are the fastest, most consistent way to control graphics, enforce standards, and surface QA issues without manual hiding.
Set up
- Plan the data: decide which parameters will drive graphics (e.g., Fire Rating, System Classification, Status).
- Create or standardize parameters as needed (Shared or Project Parameters) so the categories you target can read them.
- Manage > Filters: New filter, select categories, define rules, and name clearly (prefix by discipline/use, for example “A-FR-Walls”).
- Apply in Visibility/Graphics > Filters tab: Add your filter and set line, pattern, color, halftone, and transparency overrides.
- Save to a View Template and apply broadly for consistency and speed. For teams, publish templates via your standard content path.
Best practices
- Prefer filters over Hide in View; filters are repeatable, documentable, and template-driven.
- Limit the number of filters per view; keep rules simple for performance and clarity.
- Name filters systematically: Discipline–Purpose–Category (e.g., M-Status-Ducts).
- Order matters: when multiple filters affect the same element, filter priority follows the list order in the view; move critical filters to the top.
- Use an accessible color palette; reserve saturated colors for clash/QA, muted tones for production drawings.
High-value recipes
- Code compliance: Color fire-rated walls by Fire Rating; fade non-rated walls to emphasize egress paths.
- Scope/Status: Drive a “Status” text parameter (Existing, New, To Remain, NIC) and color-code across walls, doors, casework, MEP equipment.
- MEP systems: Override ducts/pipes by System Classification or System Type to clarify supply/return/exhaust or CHW/HW loops.
- Structural QA: Highlight structural framing with incorrect Structural Usage or beam size outliers for quick review.
- Documentation readiness: Color elements whose Keynote or Assembly Code is missing to catch annotation gaps before sheets go out.
- Worksets review: Fade non-editable or linked worksets during coordination to reduce visual noise while keeping context.
Troubleshooting and tips
- Element overrides beat filters; reset element overrides if expected filter graphics don’t show.
- Ensure the category is visible; a filter can’t display what the category hides.
- Units matter: numeric rules evaluate project units; confirm rounding and format in Project Units when rules seem off.
- Linked models: filters don’t reach inside links; use By Linked View, link display settings, or standards enforced in the source model.
- Annotation needs separate filters: model and annotation categories are independent.
- Document your filter library in your template and train the team; inconsistency often comes from ad-hoc per-view filters.
Pro move
- Combine filters with View Templates per purpose: production, coordination, QA, presentation. One model, multiple controlled outputs.
- Use Dynamo or the API to batch-apply filters and populate driver parameters at scale. If you’re growing your automation stack, consult NOVEDGE for Revit subscriptions and compatible tools.
Well-crafted View Filters elevate clarity, reduce rework, and hardwire standards into your drawings. For licensing, training, and add-ons that amplify these workflows, visit NOVEDGE.






