Hmmm, how to simplify my problem description???
Say I've got incoming data like so (NK=natural key, SK=surrogate key):
NK1, NK2, NK3
And hashed files used for lookups (reference links) like so:
NK1 --> SK1
NK2 --> SK2
And a composite key in my final lookup:
NK3, SK1, SK2
IOW, my incoming file contains 3 natural keys, I have to do two lookups, then a third lookup on NK3 plus the two SK's previously looked up.
I've set the link order in the transformer stage properly, and set the lookups for NK1 and NK2 based on the incoming data from the primary link.
But, I can't seem to drag the results of the "upstream" lookups as the key expression of the final lookup.
If the upstream lookup has succeeded (or even if it hasn't), and the result is available "in memory" for writing to the output, then why can't I also use it as input to the downstream lookup???
Thanks,
Scott
Using the results of a lookup in another downstream lookup
Moderators: chulett, rschirm, roy
Just a curiousity question: is this the same in DS 8.x? IMO, if it doesn't allow me to drag the upstream key reference, but allows me to type it in, but it still stays red, but in fact works, then it's a design bug. It may work as designed, but the design is crap
However I do understand that there may be internal, technical reasons why this would be hard to fix.
Regardless, thanks heaps for the tip. I really didn't want to have to add additional transformations (my actual problem definition is a lot more complex).
![Confused :?](./images/smilies/icon_confused.gif)
Regardless, thanks heaps for the tip. I really didn't want to have to add additional transformations (my actual problem definition is a lot more complex).
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: