Visibility property in view template not following the filter priority order

Visibility property in view template not following the filter priority order

lucdoucet_msdl
Advisor Advisor
1,006 Views
5 Replies
Message 1 of 6

Visibility property in view template not following the filter priority order

lucdoucet_msdl
Advisor
Advisor

This is unexpected behaviour specifically for the visibility checkbox in a view template for filters controlling the selection of view callouts.

 

According to the "Using filters" help for "About view filters" help for Revit 2022, multiple filters at the top of the list should have priority on filters below. When two filters are selecting the same view callout, graphic override for line color will behave correctly depending on their hierarchy.

 

The unexpected behaviour occurs when the same two filters are simply set to override the visibility of the callout in the view. The callout will be visible when both filters are selected, but the callout will be hidden if the lower hierarchy filter has visibility disabled.

Has anyone experienced this problem and found a solution/work-around?

The objective for the filters here is to have a filter to disable the visibility of all view of a type name (ex. A-500 DETAILS) then set a second filter to selectively force the visibility of a series of sheet details by their number range (ex. between A-510 and A-520). Combining both requirements into a single filter is not an option as the first filter is used for other templates.


In the screen capture below, filter A is a view range and filter B is all views of a type. The expected result is by enabling the visibility of filter A, the unselected visibility of filter B should be ignored and the callout be visible but it is not. As described above, when the same two filters apply a graphic override for the linework color (red versus blue) will work as expected when the filter are moved up and down the list.

Capture d’écran 2023-12-08 153126.png

 

 

-luc

0 Likes
1,007 Views
5 Replies
Replies (5)
Message 2 of 6

barthbradley
Consultant
Consultant

So you are trying to create a filter to unhide select elements that have been hidden by another filter at the top of hierarchy?  

0 Likes
Message 3 of 6

lucdoucet_msdl
Advisor
Advisor

No, I am trying to unhide a select elements that are being hidden by another filter at the bottom of the hierarchy.

0 Likes
Message 4 of 6

ToanDN
Consultant
Consultant

@lucdoucet_msdl wrote:

No, I am trying to unhide a select elements that are being hidden by another filter at the bottom of the hierarchy.


The order of filters is for graphic overrides, sans hide/show status.

0 Likes
Message 5 of 6

lucdoucet_msdl
Advisor
Advisor

@ToanDN 


This is not what is described in the help section "About view Filters" where it says  "... the visibility of graphic display of elements."

lucdoucet_msdl_0-1702069778987.png

 

Is your answer "sans hide/show status" personal experience or is it explained somewhere else in the production documentation and the current help section wrong? If it is expected behavior then the help documents are misleading.

-luc

0 Likes
Message 6 of 6

ToanDN
Consultant
Consultant

@lucdoucet_msdl wrote:

@ToanDN 


This is not what is described in the help section "About view Filters" where it says  "... the visibility of graphic display of elements."

 

Is your answer "sans hide/show status" personal experience or is it explained somewhere else in the production documentation and the current help section wrong? If it is expected behavior then the help documents are misleading.

-luc


1. The document you quoted is not entirely correct. 

2. I gave you the answer based on my understanding of how override/not override work, and personal experience.

 

To expand my answer.  Hide status is an override, show status is NOT an override, meaning it does nothing to the elements.  You cannot overrule an override with something that does nothing.

0 Likes