chulett wrote:Confused as to how that actually fixed the problem as there was no need to return multiple anything in the example given, just one.
Thanks guys, this thread helped me too.
Craig, I agree with your confusion. I have the same situation where I have 2 columns with an equality match on the lookup, the one column on the input stream that matches on a range in the lookup link.
One clue was the following error in the job log:
Code: Select all
lu_match_current_records,0: Ignoring duplicate entry; no further warnings will be issued for this table
While the ranges mean that we don't have multiple rows matched for any input, the definition of the lookup link only has the equality matched fields tagged as key fields. So, in terms of the fields identified as key fields, yes, there are multiple matches, but the range sorts it out.
I'm inclined to call it a bug (or at least a trap for young players).
Thanks to Ray for the answer (again).