Show your Do-map token XML please?

Hello Geoffrey,

I have generally revised the post with more information, I wrote this Friday afternoon in a hurry and later realized that the information content is quite poor. I also had to change some customer data.
 
I'll try a few more checks today. For example, whether it queries “incorrectly”, i.e. whether it really only checks for the value itself or does a kind of “wildcard” search.

I did a little bit of testing and I can tell, that there is something off with the return-values.I marked the results green (assumption based on the return values)


If I know change the values  in "active", so that they are more 'unique' - then it seems to work correctly:


For the moment, I will go with the last approach. At least for the time beeing and probably will also open a ticket.

You know, you might be hitting a 'feature' of the Map token most people don't know about!  Only place I ever saw it was in my book, and only because Shon told me about it.

If you use a simple Src-Dest Map token, and say Src is GroupType=LEADER, you are going to get the first value as a string (I think) and ALL The values as a nodeset.

This is super useful. 

But what does that mean when two columns have multiple possible matches in a 2 column select case?  I suspect you are seeing the results.

You can do this in XPATH if Map is not working, it is just slower.

load your varibale XML into a nodeset variable called $lv.table

then XPATH Of:

$lv.table/mapping-table/row[col[1]=$lv.o.bukrs][col[2]=$lv.check.groupType][col[3]=$lv.group.type]/text()

That will only work until you reorder the columns  There is a cleverer way to figure out the column names from col-defs but I am lazy and it is early in the morning here.

What I have observed is that if there are several matches and I also want the results from the several matches, then I would use a nodeset to have all the values here. For a result, I use the classic string.

Sorry for the possibly stupid question. (I may also not understand the answer of you 100%)
But I shouldn't even get into the case with “But what does that mean when two columns have multiple possible matches in a 2 column select case?”
In my 3 column case, this combination is unique in the mapping table, so I should only get one result back either way.
(either way, a bug ticket will be opened when the time comes)

Thanks for the info with XPATH and the help with the problem in general! I will definitely make a note of this option with XPATH.

I think this is a bug. The nodeset should only return multiples if it macthes the criteria, so AND your three conditions.

What I THINK is happening is when you use it as a nodeset you are getting a nodeset of answers from the first or maybe last condition. I suspect first.  Can you do a quick test, where there 3 distinctive answers for the same combo of three things.  See if you only get the first values or the last values.

I do something similar in a couple of drivers, and for me it works. I mean it works that I use multiple columns to identify a cell.

I might have understood the question wrongly.

I created a table: 3 columns (lookup1, lookup2, result):

<?xml version="1.0" encoding="UTF-8"?><mapping-table>
    <col-def name="lookup1" type="nocase"/>
    <col-def name="lookup2" type="nocase"/>
    <col-def name="result" type="nocase"/>
        <row>
        <col>lo1-1</col>
        <col>lo2-1</col>
        <col>result1</col>
    </row>
        <row>
        <col>lo1-2</col>
        <col>lo2-2</col>
        <col>result2</col>
    </row>
        <row>
        <col>lo1-3</col>
        <col>lo2-3</col>
        <col>result3</col>
    </row>
    <row>
        <col>lo1-4</col>
        <col>lo2-4</col>
        <col>result4</col>
    </row>
    <row>
        <col>lo1-5</col>
        <col>lo2-5</col>
        <col>result5</col>
    </row>
</mapping-table>


In my rule I have to local variables: lv1 = lo1-3 and lv2 = lo2-3, I would like to have them look up the row with result = result3

<actions>
    <do-set-local-variable name="lv1" scope="policy">
        <arg-string>
            <token-text xml:space="preserve">lo1-3</token-text>
        </arg-string>
    </do-set-local-variable>
    <do-set-local-variable name="lv2" scope="policy">
        <arg-string>
            <token-text xml:space="preserve">lo2-3</token-text>
        </arg-string>
    </do-set-local-variable>
    <do-set-local-variable name="res1" scope="policy">
        <arg-string>
            <token-map default-value="NONE" dest="result" source="lookup1"
                table="\[root]\system\driverset1\Test Driver\three-col-mappingtable">
                <token-local-variable name="lv1" />
                <token-map-source-col name="lookup2">
                    <token-local-variable name="lv2" />
                </token-map-source-col>
            </token-map>
        </arg-string>
    </do-set-local-variable>
</actions>


Simulator tells me that it’s working:

Test Driver :Applying policy: %+C%14CTESTPKG-sub-evt-Lookup2%-C.
Test Driver :  Applying to add #1.
Test Driver :    Evaluating selection criteria for rule 'Lookup by 2'.
Test Driver :    Rule selected.
Test Driver :    Applying rule 'Lookup by 2'.
Test Driver :      Action: do-set-local-variable("lv1",scope="policy","lo1-3").
Test Driver :        arg-string("lo1-3")
Test Driver :          token-text("lo1-3")
Test Driver :          Arg Value: "lo1-3".
Test Driver :      Action: do-set-local-variable("lv2",scope="policy","lo2-3").
Test Driver :        arg-string("lo2-3")
Test Driver :          token-text("lo2-3")
Test Driver :          Arg Value: "lo2-3".
Test Driver :      Action: do-set-local-variable("res1",scope="policy",token-map("\[root]\system\driverset1\Test Driver\three-col-mappingtable","result",default-value="NONE",source="lookup1",token-local-variable("lv1")+token-map-source-col("lookup2",token-local-variable("lv2")))).
Test Driver :        arg-string(token-map("\[root]\system\driverset1\Test Driver\three-col-mappingtable","result",default-value="NONE",source="lookup1",token-local-variable("lv1")+token-map-source-col("lookup2",token-local-variable("lv2"))))
Test Driver :          token-map("\[root]\system\driverset1\Test Driver\three-col-mappingtable","result",default-value="NONE",source="lookup1",token-local-variable("lv1")+token-map-source-col("lookup2",token-local-variable("lv2")))
Test Driver :            token-map("\[root]\system\driverset1\Test Driver\three-col-mappingtable","result",default-value="NONE",source="lookup1",token-local-variable("lv1")+token-map-source-col("lookup2",token-local-variable("lv2")))
Test Driver :              token-local-variable("lv1")
Test Driver :                Token Value: "lo1-3".
Test Driver :              token-map-source-col("lookup2",token-local-variable("lv2"))
Test Driver :                token-map-source-col("lookup2",token-local-variable("lv2"))
Test Driver :                  token-local-variable("lv2")
Test Driver :                    Token Value: "lo2-3".
Test Driver :                  Arg Value: "lo2-3".
Test Driver :                Token Value: "[lookup2, lo2-3]".
Test Driver :              Arg Value: "lo1-3,[lookup2, lo2-3]".
Test Driver :            Token Value: "result3".
Test Driver :          Arg Value: "result3".


The only difference I have is that after <token-map.. my first node is a local variable: <token-local-variable name="lv1" />, everything else is the same.

It might work it might not.