Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
There is currently no "Or" capability in filter rules, which makes it very difficult/inefficient at times to filter. For instance: assume I only want to see walls that contain CMU or Concrete in the type name. I can create a filter for Just the concrete walls easily, and do the same for the CMU. But one filter with OR could easily accomplish the task.
The filter interface could use a lot of improvements, being able to select from any parameter would be a good start. Maybe keep the current interface as default, but add an "Advanced" button, which allows you to build a better query, say like Navisworks' "Find Items" dialog?
I never specified that this post was about view filters. Any filter should have the ability to put an "or" or "xor" between rules/sets of rules. Ideally we would be able to simply re-use filters we've already created and apply them to schedules instead of re-creating the same rules on schedule filters.
This is the biggest frustration when trying to create filters of any sort, but most specifically Scheduling. Often the work-around is "create a dummy parameter to find what you want to filter for" and that's rather ridiculous.
Thanks for your submission and votes on this idea! We are evaluating where this request falls into our roadmap and will provide an update when we have made a decision.
Awesome. Since Revit is a database (hopefully relational) then I think that putting together arbitrary Boolean queries is not really the problem. It feels to me like a UI problem.
Please add all logical operators whilst you're at it. Also increase number of filter rules above 3 (8 perhaps) or option to add rules. Maybe the Navisworks find all interface would be a good starting place.
It would be great to be able to add a sorting and filtering criteria as needed. In other words, if I need another criteria for sorting, I would like to have an "ADD" button. For filtering, in addition to "ADD" button, we need logical "OR"
I've been creating filters a lot today and OR filters would really make it a lot easier.
Also three rules are way too much, especially if you start to use OR conditions. Ideally we would be able to add as much rules as needed and have an option to nest them. For instance
What we need is an interface like this one: http://querybuilder.js.org/ It allows for the creation of arbitrary queries/filters that use Boolean logic.
This is just an image but if you go to the URL you can play around with a live demo.
