Bringing parity to SQL lookup and SQL validation (in in database)

OK here I am scratching my head , trying to understand how is in list validation work

I have a text file list which contains
31146
31148

I have a csv containing orders which contain
31146

1. When I select IS IN LIST - When execution is SUCCESSFUL - DISCARD RECORD , as per my understand 31146 is supposed to be discarded ? Is this the right behaviour ?
2. Also when multiple validations are present , I assume it's on OR mode , even if 1 validation is True , it rejected ?

1. When I select IS IN LIST - When execution is SUCCESSFUL - DISCARD RECORD , as per my understand 31146 is supposed to be discarded ? Is this the right behaviour ?

Correct, (you can always press preview button and see it your self)

2. Also when multiple validations are present , I assume it's on OR mode , even if 1 validation is True , it rejected ?

Correct, everything must succeed in order to be passed to success path

www.etl-tools.com/wiki/advanced-etl-proc...ming-data/validator/
 

I am uanble to get predictable result from Validaiton . I have treid from last 90 min. I am attaching my transfromation , my input file and my validation file

the input file contains
"expo"
"30934"
"30939"
"30985"
"12345" ---> ONLY VALUE NOT IN master list

When running validation ,which I have attached, using IS IN LIST (failure->reject) , 12345 should be rejected but isn't the case

 

"12345" does not equal to 12345 therefore transformation is not not working

open expohead_unshipped.csv in notepad and remove double quotes than it should work  

admin wrote:

"12345" does not equal to 12345 therefore transformation is not not working

open expohead_unshipped.csv in notepad and remove double quotes than it should work  

Almost everywhere else the Quoting feature (double quotes) is available as text qualifier except this validation window !

 
 

Well if you think about about it there us no need to use delimiter or quote for "Is in list" function because there is only one field