One more info. From DSLink11 I am not taking any value. This is just for look up.if the look up does not match, just forward all the values from Dslink10. This is waht I want to do.
dsusersaj wrote:To avoid any confusion. ..
The constraint in my job is DSLink11.NOTFOUND.
Still the rows doesnot pass the transformer. The table doesnt have them now.
dsusersaj wrote:I am sorry i did give dslink11.notfound.
I pasted the wrong this first.
kumar_s wrote:Not of NotFound = Found. Use just DSLink11.NOTFOUND.
Wondering, how did it match the first time if the Hashed file is empty. ...
The problem is resolved. I just directed the look up table's data to a hashed file. I was thinking table as reference would work the same way as hashed file. But it was not though.
Good that you resolved it. Table in reference link should work same as Hashed file in this matter. May be other changes in the jobs should be noted down.
Not sure what is DSLink11. If you are checking for Null, check for the column which will be populated with Null when not found.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
I'm curious why everything (subject, first post, etc) states you were having a problem with a hashed file lookup and now suddenly it works if you use a hashed file?
-craig
"You can never have too many knives" -- Logan Nine Fingers
I was also thinking the same that hashed file would work the same way as table. This strong belief made me post the way I did. Referencing table as hashed file.But in the later post I clarified it as table I believe.
kumar_s wrote:Good that you resolved it. Table in reference link should work same as Hashed file in this matter. May be other changes in the jobs should be noted down.
Not sure what is DSLink11. If you are check ...
Umm, no. All you managed to accomplish by not stating your problem accurately was cause two pages of thrashing to occur when it could have been solved in one or two responses had you correctly described what you were doing.
Please keep that in mind in the future. The more information and the more pertinent details we have, the better we can help you solve your issue.
-craig
"You can never have too many knives" -- Logan Nine Fingers
chulett wrote:Umm, no. All you managed to accomplish by not stating your problem accurately was cause two pages of thrashing to occur when it could have been solved in one or two responses had you correctly described what you were doing.
Please keep that in mind in the future. The more information and the more pertinent details we have, the better we can help you solve your issue.