|
Home > Archive > BizTalk Server Tools > September 2004 > (Additional info) BTS 2002 Mapper Question
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
(Additional info) BTS 2002 Mapper Question
|
|
|
| An attempt to clarify:
I am trying to use these values within mapper functoid logic (not simply
moving values from INPUT file to OUTPUT file, this works fine). For example,
the first keyedvalue element will cause a certain functoid logic to occur,
while the second keyedvalue element will cause a different functoid logic to
occur.
I have been able to use the "INDEX" functoid to get the "KeyName" element
value, but using the same logic for the "KeyValue" element results in an
empty string for the second instance of the KeyedValue element.
Thanks,
BJ
"BJ" wrote:
> The following xml is buried 5 levels deep (from the root) in a document. I
> am having trouble getting the "KeyValue" of the second instance, it always
> returns an empty string. I am able to retrieve the "KeyName" of the second
> instance as well as both "KeyValue" and "KeyName" for the first instance,
> with no problem.
>
> <KeyedValue id="MarketingStrategy_1">
> <KeyName>WorksiteIndicator</KeyName>
> <KeyValue>N</KeyValue>
> </KeyedValue>
> <KeyedValue id="MarketingStrategy_2">
> <KeyName>WithdrawnIndicator</KeyName>
> <KeyValue>N</KeyValue>
> </KeyedValue>
>
> Thanks,
> BJ
| |
|
| Got it. The indices were slightly off (looked at XSLT directly to discover
problem).
"BJ" wrote:
[vbcol=seagreen]
> An attempt to clarify:
> I am trying to use these values within mapper functoid logic (not simply
> moving values from INPUT file to OUTPUT file, this works fine). For example,
> the first keyedvalue element will cause a certain functoid logic to occur,
> while the second keyedvalue element will cause a different functoid logic to
> occur.
>
> I have been able to use the "INDEX" functoid to get the "KeyName" element
> value, but using the same logic for the "KeyValue" element results in an
> empty string for the second instance of the KeyedValue element.
>
> Thanks,
> BJ
>
> "BJ" wrote:
>
|
|
|
|
|