We have a unique number 0 and 00 to identify paying customer.
I set (0 and 00) in the AttributeFilter but both values end up on either 0 or 00 depending on wich one in the list comes first.
What am i missing here? or should i set up a tester instead for each number or text value?
/Tim
Best answer by david_r
I'm suspecting that the AttributeFilter is using some sort of 'intelligence' to decide whether to make the comparison as string or as an integer. In this case it seems like it's doing an integer comparison: 0 == 00.
If you switch to using the TestFilter, you can force the use of a string comparison: 0 != 00
For example:
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
I'm suspecting that the AttributeFilter is using some sort of 'intelligence' to decide whether to make the comparison as string or as an integer. In this case it seems like it's doing an integer comparison: 0 == 00.
If you switch to using the TestFilter, you can force the use of a string comparison: 0 != 00