Solved! Go to Solution.
You may have already tried this - and this may not be your issue at all - but in case it is, it's always good practice to handle nulls before using fields...
row1.account_type != null && row1.account_type.length() > 0 : row1.account_type.equals("Parent")
You shouldn't be using the filter in that way. That condition is handled by the join on the input. If you have an inner join it will not pass any Collateral records to the output.
The NullPointer Exception comes from trying to do a function on a collateral field when there hasn't been a match. Check for null in the rule.
For example in rule for escrow put
before existing rule and ) at end.
But if you use an inner join for input none of the fields will be null unless there's nulls in the data.
Yes sorry. should be
! Relational.ISNULL(value)?rule true:rule false
It's difficult to see what's in your rules from the picture.
Firstly the rule is wrong. All you need is
but this isn't where the problem is as there's no function done on the data.
Look on your code tab for the line being flagged as the null pointer exception and it will tell you where the problem is.
You probably don't need the isEmpty check.
It's because you're doing the replace before checking for null (I think). So you need to do the isnull and then replace if false.
row1.TRINAMETX != null ?
/* your code here when row1.TRINAMETX is null */
Join us at the Community Lounge.
Talend named a Leader.
Kickstart your first data integration and ETL projects.
Watch the recorded webinar!
Pick up some tips and tricks with Context Variables
Learn how media organizations have achieved success with Data Integration
Create systems and workflow to manage clean data ingestion and data transformation.