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 secon
d
> 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

[ Post a follow-up to this message ]

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 examp
le,
> 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:
> 

[ Post a follow-up to this message ]