First off, you can't (and/or really shouldn't) use:
>
<
=>
=<
(filter) rules for text values - so that's a dead duck.

...and since <Function> is also a text parameter, that's very much a dead-end false-promise as well.

Here we have a type naming strategy for all things where "_S_" is enough to capture everything we need - but we're architects, and I anticipate since you're talking structural walls specifically you're structure and will need to go a little deeper with your information... not to worry, there are plenty of other parameters you could use...


I'd be inclined to suggest you get populating the <Assembly Code> myself, even if you don't use the classification form, as it really, really helps... as you can basically "drill" with filters like:
Walls - Assembly Code - begins with B
Walls - Assembly Code - begins with B10
Walls - Assembly Code - begins with B1010

Why do you call using a filter for that, a workaround? Seems like a totally fine way to to it. Just apply it to your view filter and be on your way!

add a shared parameter easy to do, make it an on/off parameter and simply assign a filter using that new parameter and have them hidden or not in view based on the presence (or not) of the shared parameter being activated.

similar situation myself. Some SE's wont start modelling till they get some setting out information from the Architect. Then once they get that and model it up, they'll go over what can and cant be achieved ./ needs redesigning. its easier to keep that in the one architectural model. then filter it out later. But as the original poster says, there is no filter for Yes/no structure for walls like there is on floors.

I'd avoid the adding of a shared parameter road, as when it comes to exporting IFCs. you'll have to make sure your IFC parameters are pathed correctly. Custom parameters are fiddly to do this and you need to do this to anyone using IFCs eg in navisworks. then they can filter things correctly. the more you deviate from the in built parameters. the more awkward things will get when working with others and the tools they may have.

I noticed when you tick on Structural for a wall. you get the "structural usage" instance parameter appear. This is normally greyed out and says "non bearing" unless structure is ticked. So how i worked around it. I just made a filter for Structural usage equals "non-bearing" and unticked visibility. That hides all my non structural walls. It works as a work around but surprising this is an issue still in rvt 2019!

I'm pretty sure that Walls do not have the Structural yes/no available in Filters precisely because of the different structural use types.

I'm not even sure why the original question was posed. Using Structural Usage in the filter certainly is not a workaround. It's how it should actually work. Simply set the filter to capture all walls where Structural Usage DOES NOT EQUAL non-bearing, apply the filter to the view, and set the filter's visibility to Off. Quick and easy. Nothing extra needed.