Hi @Hamza_rashed,
Thanks for your feature suggestion!
We believe a native OR/Nested Filters will better address your issue. Although our annual goal is to deliver a full as-code product, we are planning to prioritize this feature in Q4 this year. We’ll keep you informed about the progress of this feature.
In the meantime, as @SterlingParamoreMSE stated above, our Query Param feature can also solve this issue, but it is a 4.0 feature, and the solution is quite hacky IMHO.
So for your case:
- If you are using Holistics 4.0 version, your issue can be addressed by our Query Param feature.
- If you are currently using Holistics 3.0 version and are interested in migrating to our 4.0 version, please feel free to contact our Support Team to request a version migration.
- If you are currently using Holistics 3.0 and don’t want to migrate to our 4.0 version, I’m afraid that this issue is only solved when we support the OR/Nested Filters feature.
Feel free to let us know if you need further support. We are happy to assist you