Skip to main content

Graphic Overrides When Inserting Details with Pirros

What graphic overrides, filters, and visual settings carry over when you insert Details into a Project using Pirros — and what to check when they don't.

When you bring Details into your Project using Pirros Insert, Revit handles graphic overrides the same way it handles them with Insert Views from File. Most view-level settings come through cleanly, but a few Project-level settings don't. Here's what to expect — and what to do when something doesn't look right.


Pirros Insert here means bringing Details in with either version of the Pirros plugin: Insert (or drag-and-drop) on the Browse tab of the Pirros panel in Pirros in Revit, or Download on the Pirros ribbon tab in the classic plugin. Where the two behave differently, this article says so.

Which plugin do you have? Look at the Pirros tab in the Revit ribbon. A single Pirros button that opens a docked panel with Browse, Updates, Sync and Settings tabs means you have Pirros in Revit. Separate Sync, Download, Settings, Pirros and Live Link buttons mean you have the classic plugin. Don't go by the version number alone: on Revit 2020–2023 the classic plugin can show a 4.x version number.

What transfers

View-specific Visibility/Graphics overrides

Any overrides applied directly inside a view — via the Visibility/Graphics dialog (VG) — travel with the view. Category overrides, line weight changes, color overrides, and halftone settings set at the view level are all retained.

Element-level overrides (By Element)

Overrides applied to individual elements via Override Graphics in View → By Element — including Halftone, line color, line weight, projection and cut patterns, and transparency — travel with the Detail. If a specific window, beam, or other element was set to Halftone in the source view, that override is preserved when the Detail is inserted into your Project.

Pirros in Revit carries these element-level overrides over when it inserts a Detail, and so do newer versions of the classic plugin. If element-level overrides such as Halftone don't come through when you download with the classic plugin, your classic plugin version doesn't carry them over: it keeps only the fill pattern overrides on filled regions.

The overrides also have to be in the Detail on Pirros. Pirros in Revit and newer classic versions keep element-level overrides when they sync a Detail; older classic versions keep only the fill pattern overrides on filled regions, so Details synced with them don't include other element-level overrides.

Filters and their graphic overrides

Filters assigned to the view are imported along with their graphic override settings (line color, fill pattern, transparency, etc.). As long as the filter's rules can resolve in your Project, they'll work as expected.

What may need attention

Filters referencing Project-specific parameters

If a filter is based on a shared parameter or Project parameter that doesn't exist in your destination file, the filter will come in but won't function correctly. The graphic override settings will be there, but the filter won't return any elements until the parameter is added to your Project.

What to do: Check the Filters tab in VG after inserting. Any filter with a missing parameter will typically show a warning. Add the shared parameter to your Project to restore filter behavior.

Object Styles

Object Styles are a Project-level setting, not a view-level one. If the source detail uses customized object styles (custom line weights or colors for a specific category), those won't override your Project's Object Styles. Your Project's settings take precedence.

What to do: If Details look different than expected, compare Object Styles (Manage → Object Styles) between the source and your project. Adjust your Project's Object Styles if visual consistency is critical.

Phase and Design Option overrides

If a view is set to a specific phase or design option that doesn't exist in your Project, Revit may show warnings and phase/design option graphic overrides may not display as intended.

What to do: After inserting, open the view's Properties and verify the Phase and Design Option assignments. Update them to match your Project's phases.

Linked file overrides

Visibility and graphic settings applied to linked files within a view don't transfer if those links aren't present in your Project. These overrides can be safely ignored if the links aren't relevant.

Quick reference

Setting

Transfers with Pirros Insert?

View Visibility/Graphics overrides

✅ Yes

Element-level overrides (By Element)

✅ Yes

Filter graphic overrides

✅ Yes

Filter functionality (rules)

⚠️ Only if parameters exist in destination

Object Styles

❌ No — Project-level setting

Phase graphic overrides

⚠️ Only if phase exists in destination

Linked file overrides

❌ No — link must exist in destination

💡 Tip: Before inserting a Detail, confirm that any shared parameters used by its filters exist in your Project's shared parameter file. A quick VG check after inserting will surface anything that needs attention — filters with missing parameters will appear with a warning.

Did this answer your question?