Filter improvement: Having both "and/or" logic when selecting multiple filters/tags when searching

​Hi  ​@Markus Pettersen!

Thank you for suggesting this product idea. We will follow the traction this idea gets in the community. You can expect updates on this post if we decide to include this in our future roadmap, or if we require more information.

​

Hi ​@Markus Pettersen !

Some background on the filter logic, and would love your feedback on this. 

In filters, each filter key/property typically has several values each. If you select several values for the same key, these are treated with the OR operation, while between keys we apply the AND operation. Examples: 

• In the filters, you select the key “network level”, and two values. This selection is treated as: network level = production_subsystem OR production_system. 

• If you select another key in addition, this selection is treated with the AND operation: (network level = production_subsystem OR production_system) AND product_type = Gross.
   

From what you share, you expect there to be an “AND” logic between selected values for a key? I’m wondering how widespread this logic is - as most keys would have just one value per data instance, e.g. for most keys, selecting more than one value with AND logic would yield 0 results. 

Is it some specific keys/properties, like e.g. “list of strings” property types, that you expect AND logic? 

Best, 
Sofie Berge, Product Manager

Thanks for the clarification ​@Sofie Svartdal Berge. It makes sense that when selecting values across properties it is AND, and I see the reasoning for the OR logic when selecting multiple values for a property. However, in my specific use case it is the use of “tags” as a way of quickly identifying and filtering time series rather than creating an elaborate extension to the core data model to enable the same feature.

It is possible for me to model this, but not directly in the core data model. This means I would need to create an extension to the core data model to simply enable better filtering options, which does seem to be a bit overkill for a use case consisting of needing to filter time series based on a couple properties. Filtering options in the UI is now my only reason for considering making an extension of CDM, which would make the development a bit more cumbersome.

Tags were used in this instance as a replacement to the classic metadata, it worked great when only filtering on one tag, would just be nice if worked well with multiple.

To summarize, my point is that not all properties are equal, in your example the implemented logic makes sense. For my use case, maybe not so much. This may be a difference between properties with a single value and those with lists (like tags). And just to be very clear, I am not suggesting replacing the OR logic, but consider adding an AND in addition (maybe just for tags, or maybe just for properties with list values).

Regards,
Markus Pettersen

Hi!

Then we are one the same page - I can see the value for properties of type list of strings where one data instance can have several property values. 

I’ll add this feature request to our backlog. 

Best, 

Sofie