I would like to copy filters from multiple views and combine them in one single view. I'm getting to the point where one view has what I need and I want to compare it with another view. The current solution is to hire an engineer to write a script or painstakingly rebuild one filter onto an existing one.
I've seen this idea before and will hope a new 'request' will resurface the need for more reusable functionality around filters.
Hi, I don't think script can help, as views has no methods in scripting to read or write their filter conditions. The only thing you can get is a list of records. Of course, you can write a script to see how much records seen in combined 2 or 3 views, but I doubt you will use it often. What I can say - if your view became so complex that you struggle to combine a filter from several views, you can transfer it to a formula, add it as a field and thus simplify it to a single condition.
Actually it's {Name} is not empy => IF({Name, {Name} contains 'son' => IF(FIND('son', {Name} ), the rest mostly "as is". To hardcode exact date in formula , use ISO format 'any of', 'none of' => use FIND rather of '=' array types like Lookup - sometimes need &"" or CONCATENATE() to convert to string
often you can use math and text functions to shorten, like Owner type = ... and there are 8 possible types, where you need 3 of 8 and all begins with "Owner..", while others 5 - no. So, it can be IF(LEFT({Owner type},5)='Owner' , .....)
I also tried to screenshot the filter, give it to chatbot and asked for formula. With minor fixes, it worked. You can't rely on chatbot without some knowlewdge on a subject and without verifying it's result (at least number of records filtered) . But it's a good helper for simple and routine things, like Formulas, REGEX and T-SQL
It's been a long week, so I apologize in advance if this is an obvious question; if I create a filter formula field, do I just filter off of that field?
Yes, if you verified and all records shown are 'YES' and filtered out are 'NO' (for example) , then simple filter by {Formula field}='YES' will do the same as filter before. Of course, you would better give it a descriptive name, maybe according to a name of a view. It also decreases a chance for a typo or missed condition, when you combine several complex filters
I just duplicating view and gave it descriptive name in such case. But in fact, I cannot disagree with you - while I working 'above the data' most of time, and don't need complex filtering, users sometimes asking me to assist with filter, when nesting level became complicated.
