Hi!
I tried using several client filters for the same property, but it seems like it does not work.
I thought it would add the filter on top of the other, example:
I have Object.Status = “Created” on one filter and Object.Status is any of “Archived”, “Read” on the other filter and both filters are true.
I thought it would apply both filters which results in Object.Status is any of “Created”, “Archived”, “Read”, but instead it just shows no objects when both filters are applied.
Hello Sigve,
All enabled Client Filters are applied in order.
So your current setup most likely gives you the equivalent filter:
Object.Status === Created
ANDObject.Status === Archived
OR
Object.Status === Read
I am assuming that Object.Status is a single cardinality property? In that case you are essentially asking for an Object where Status is both Created AND Archived or Created AND Read at the same time. But Status can only be one value, and not two at the same time, so all results are filtered out.
Does that make sense 
?
// Erik
Hi Erik!
That makes sense. We also tried with Object.Status is any of “Created” and Object.Status is any of “Archived”, “Read” on the other filter. Would that give:
Object.Status === Created
OR
Object.Status === Archived
OR
Object.Status === Read
Or would it also be AND between the filters? Is it always AND between the filters?
I think it’s easier if we split up the filter operations.
Imagine this dataset:
| Object Number | Status |
|---|---|
| 1 | Read |
| 2 | Archived |
| 3 | Created |
The first filter will check if Object.Status is any of Created. After the filter has been applied, the remaining object will be:
| Object Number | Status |
|---|---|
| 3 | Created |
Then we run the second filter which checks if Object State is either Archived or Read. None of our remaining objects matches this filter. So nothing is returned.
So you could say that there is an AND between all filters, but in reality, every filter is evaluated one by one in order
// Erik
Ok, I understand, thank you for the clarification! 