Lookup retruns 0 instead of null for records not found
Posted: Tue Jun 07, 2011 9:29 am
Hi, thanks for reading.
Have a job that calls a shared container. The shared container performs a common lookup. The shared container is using RCP so on the input link we only define metadata for fields needed in the lookup...everything else passes through via rcp. Everything works, as far as the rcp and lookup, but when the lookup fails we get 0 in our integer field and 01-01-0001 in our two date fields. These are fields that we are expected to get from the reference link, but are expecting nulls when there is not a match. Seems to be defaulting...anyone know what I can change to get nulls in fields when a match isn't found?
Have a job that calls a shared container. The shared container performs a common lookup. The shared container is using RCP so on the input link we only define metadata for fields needed in the lookup...everything else passes through via rcp. Everything works, as far as the rcp and lookup, but when the lookup fails we get 0 in our integer field and 01-01-0001 in our two date fields. These are fields that we are expected to get from the reference link, but are expecting nulls when there is not a match. Seems to be defaulting...anyone know what I can change to get nulls in fields when a match isn't found?