ALV: multiselect selects more rows than expected

[Former Member]

If I have table with many pages of data and do following actions:

1) leave lead select in first page as it is

2) go to next page - with ctrl select 2nd row

3) go to next page - with ctrl select 1st row

4) go back to previous page - 2nd row selected as expected

5) go to next (3rd) page - 1st and 2nd row is selected (expected only 1st row to be selected)

There is no any select event handler which could cause such behavior.

I have noticed such error on standard table, too.

What is causing this error?

[tina_yang]

Oskars,

If you are using

-- one context node for this table,

-- you have set the context node's Cardinality to o...n,

-- and the table UI element that's bind to this context node's property SelectionMode is set to be 'auto' or 'multi',

then I think this is a bug in your version. I have tried on my system (SAP ECC 6.0, SAP_ABA 700), and I cannot reproduce the behavior you have describe in this thread. Check the CSN to confirm if this is a bug indeed.

regards,

Tina Yang

[Former Member]

System version SAP_ABA 700 Level 10.

I checked notes, but all similar errors are already resolved in current version.

[Former Member]

Hello,

If you are using the same context node, then I suppose it is behaving correctly.

Regards,

Neha

[Former Member]

Yes, I'm using one context node per table.

So, can you explain why this behavior is correct? User selects three rows, but control returns, that there are four rows selected.

[Former Member]

In such a case, the behaviour is not correct (I thought you had a single context node for all the tables).

Just check in you code, whether you are setting the lead selection in some place (By code)

Regards,

Neha

[Former Member]

So, there is no custom code running between row selections.

I changed attribute "Initialization Lead Selection" to 'false' for this context node in component controller, but still no changes to weird behavior.