Joined: 21 Dec 2007
Online Status: Offline
Posts: 4374
Posted: 08 Jun 2011 at 9:59am
what does the code look like? seems odd, that it would behave like that. I am assuming that the value to be tested for equality is in the array as well.
Joined: 01 Dec 2010
Online Status: Offline
Posts: 386
Posted: 13 Jun 2011 at 3:11am
Tried that as well.
I tried some simpler conditions like {?param1} = "this" or {?param2} = "that" but even that resulted in the same behavior.
Can't imagine where the problem might be.
When switching the order of the conditions, I get two distinct set of results.
It's possible that my data is not actually what I expect though, but after checking it, doesn't seem to be the case.
EDIT: I decided to print out the boolean value in a formula and it definitely does seem to be checking only the first condition. At least, it doesn't print true when it should when the second condition is met.
Joined: 01 Dec 2010
Online Status: Offline
Posts: 386
Posted: 16 Jun 2011 at 3:29am
Found the problem.
I wasn't checking for null values.
The clue was when I was doing a simple {field} <> ' ' and then only the fields that had a value printed True while the others didn't even print anything.
The proper conditions should be
(not isnull({field1}) and {field1} = ...) or (not isnull({field2}) and {field2} in split(...))
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum