<@U3VNY94VB> try a simple case statement as criter...
# suiteanalytics
j
@dbarnett try a simple case statement as criteria: case when {custrecord_fieldId} like '%<%' then 1 else 0 end (Set it as a criteria filter and get all with values of one) The statement if you want to get all values that contains the < character
d
@Jacob no luck there either unfortunately, still came back with 0s on everything even when containing
<
j
weird. Can you send a screenshot of the criteria and a sample of the field with the value <
g
This intrigued me, and while i'm not sure of the specifics of the search/data @dbarnett is using, I tried adding a
<
to a text field on a customer record. Same results: 0 I changed it to
=
thinking perhaps it is because they are both comparison operators that causes the formula to not work. the
=
worked. very bizarre
d
@Gregory Jones thanks for jumping in 🙂 not sure what exactly you entered though, I am testing
CASE WHEN {custrecord_fieldId} = 'BasePack0001<>' THEN 1 ELSE 0 END
now, but still getting 0s
g
I tried something along the lines of
case when {notes} LIKE '%<%' THEN 1 ELSE 0 END
to test if it would pick up the
<
which it didn't. I also tried
INSTR({notes}, '<')
and got 0 as well. Then when I switched over to
=
i was getting accurate results for both formulas
d
@Gregory Jones so the same as my formula essentially but getting the expected results? or are you saying you switched to searching for the
=
character instead of
<
?
g
I replaced the
<
in the field i was searching on with
=
, then updated my formulas to search for
=
instead of
<
and that's when it worked.
d
oh ok , sorry I misunderstood initially. yah it just seems to be something in particular about the
<
or
>
symbols it doesn't like. I assume
=
and many others behave as expected
g
No worries. Yeah, seems like there is some underlying rule about those characters. I tried searching suiteanswers as well as google - but came up empty.
g
I wonder if the underlying data is not actually < > but something like > and <
d
@George McMullen nice call, that worked!
I actually thought about that, like if was encoded if I had copied from a Url or something, but I figured since I explicitly typed out the characters into the field, it wouldn't be that issue 🤷‍♂️
g
Awesome! Glad it worked out!
👍🏻 1
j
Great to know this..Thanks!