04-27-2023 06:55 AM
I’m using join snap to with a condition NOT, surprisingly the validation is giving me output, but when i’m running the pipeline it is giving me an error, Can someone please help me understand what i’m doing wrong
ERROR message: Not comparable objects: String abc and Boolean false
05-01-2023 11:33 PM
Hi Can anyone help me with this?
05-02-2023 07:25 AM
Hi @dd_snaplogic,
The two entities that you’re trying to compare, should be of the same data type. Adding a !(not) in front of your $abc field which I presume is of a type String, will turn that field into a boolean value - false. So you’ll end up comparing boolean and string.
If I understand correctly, you want the records that do not match? If that’s the case, you can open an error view on the Join snap, and select the ‘Unmatched data to error view’ option:
Hope this helps,
Regards,
Bojan
05-02-2023 07:47 AM
@bojanvelevski / @dd_snaplogic - I would recommend against sending all of the unmatched to an error view. These errors wind up in the jcc.logs and can cause space issues if there is a large volume of records that go down that path.
Instead, I would recommend that you use a Left Outer join condition and either Filter or Router the results for matched and unmatched records.
05-10-2023 09:33 PM
@bojanvelevski Yes i saw that options of sending unmatched data in error view, but that will also send the data to my error pipeline so route options to error view is not an option.
At the end i used the path similar to what @koryknick suggested. used left outer join and with a filter $input1_abc ==null as my condition for unmatched data.
I do remember earlier it was not like that, I could use !(NOT) condition in the path itself and it used to work.