Skip to main content
Solved

Unique values in AttributeFilter end up as one value.

  • December 9, 2022
  • 2 replies
  • 17 views

timnil00
Contributor
Forum|alt.badge.img+6

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:

image

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.

2 replies

david_r
Celebrity
  • 8391 replies
  • Best Answer
  • December 9, 2022

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:

image


timnil00
Contributor
Forum|alt.badge.img+6
  • Author
  • Contributor
  • 6 replies
  • December 9, 2022

Okey, well this seems to work, thank you so much :).

 

2022-12-09_13-43-30