Unexpected behaviour of Contains(...) function

[Paul_s_Moody]

Hi,

As part of a data cleansing workflow that is replacing an Excel workbook I'm using the content of one column to (in theory at least) generate a new column that should contain a True/False result. However, all records are being set to False rather a mixture of True and False as the data would suggest

To test this and see if something silly is going on, I've changed the formula to generate a string True/False and append the column containing the original data to the result. However you can see in the "test" in the configuration that the record in question DOES contain the text that I'm looking for, but is returning a false.

I'm sure it's just something silly in the way that I'm using the Contains(...) function, but I can't see anything obvious. 

I also get the same issue if i put the string I'm looking for in either single '   ' or double "   " quotes...

Can anyone suggest a way to solve the issue?

Thanks in advance

[ChrisTX]

Instead of "True" and "False", use

1 for True

0 for False

Chris

[DataNath · Accepted solution]

Hey @Paul_s_Moody, the Contains() syntax should be Contains([FIELD], <Check>) - you're currently doing this the other way round i.e. Contains(<Check>,[Field]). Example:

How yours is currently set up:

[Paul_s_Moody]

Thank you!

Glad it was just something daft in my formula!