1 of 1 people found this helpful
It would be helpful to have the query you're using, but one thing I'm guessing at (and have used myself) from your proposed logic is:
All conditions (AND)
Client is equal to: ABC
priority is equal to: P2
priority is equal to: P3
Basically you want your OR logic to be contained in parentheses. The logic you provided would be two different groups and return everything: 1) Client ABC nodes that are priority 2. 2) Any P3 nodes.
What you want is any P2 or P3 nodes from client ABC so you need to put the OR into a parentheses so it would be 1) Client ABC nodes that are P2. 2) Client ABC nodes that are P3.
As for why the P3 nodes shouldn't be returning at all, my guess would be to check the client custom properties are what you'd expect or knowing more about what you're exactly trying to get out of them as the data would presumably not be there (though it looks like you tried to account for that).
As it happens, between asking that question and seeing your reply I have now been on an 'intro to SOLW' course and alerting / reporting logic was one key query I was looking to get answered, I didn't share the query due to confidentiality reasons but you managed to work out what I was after so, thank you. Then of course I thought, well I could just blank the 'private' sections so:
Essentially I needed to think of the logic as being like BODMAS or PEDMAS where brackets are always done first so my query needed to read:
ALL Below conditions are met (AND)
Condition 1 - Client is = ABC
Condition 2 has to be one of the following (AND & OR)
AND it is defined as a P2 priority
AND it is defined as a P3 priority
Or to include the brackets:
[ Client = ABC + [ Priority = P2 OR P3 ] ]