Originally posted by: SystemAdmin

Hi All,
I use LOOKUP function in a single map rule, like this:

=TO_XML_DEL_CLIENT(
LOOKUP(SETPRTY:SETDET Sequence:inputCard, q Party_C AttValue:Party_C AttList:Party_C Class:SETPRTY:SETDET Sequence:inputCard = "SELL"),

LOOKUP(SETPRTY:SETDET Sequence:inputCard, q Party_C AttValue:Party_C AttList:Party_C Class:SETPRTY:SETDET Sequence:inputCard = "DEAG"))
But the second lookup returns NONE in every cases no matter what is the input source card.
Where is an error?
Is it possible to use lookup functions for the same input parameter type in a map rule?
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: TarunB

Hmmm if I remember correctly this is due to a data binding issue whereby the first lookup locks into a result and the second lookup on the same source (in the same rule) is unable to shift away from this result.

To counter this try to duplicate the source card (or copy it to a sink output card) and perform the second lookup based on there. Or perform the lookups in a separate card and use the results in your card with the rule below.

Par example, as resolved by my old friend Laurent here:
https://www.ibm.com/developerworks/forums/thread.jspa?messageID=14014571&#14014571
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: TarunB

Ah I see your almost identical question was answered already here.

https://www.ibm.com/developerworks/forums/thread.jspa?threadID=273720&tstart=0
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender