I have put two data tables A en B in one screen. In each table I place a list with three records.
The problem: when I jump around between record 1 of table A and record 1 of table B the onselectionchange does not fire. More precise if I jump for record x of table A to record x of table B the onselectionchange does not fire (and x is one and the same record number).
I use the onselectionchange for a master-detail screen: on the onselectionchange of the master I fetch the details which belongs to that master. When a user selects a different master the details are fetched. So above problem prevents me from building this master-detail screen (A is master and B is detail). E.g. a sequence of steps which show the unwanted behaviour:
Step 1: Table A => select record one (so the details of record one are presented)
Step 2: Table B => select record three
Step 3: Table A => select record three, onselection change does not fire, table A now "thinks" that record three is selected, the required behaviour is the onselectionchange trigger to fire so that detail records of master record three are presented. If I would have jumped on master record one, which is already selected, then indeed the onselection change does not need te be fired.
I think that if you jump around in different fields of one recored in the same table then the onselectionchange should not fire but if I jump between two different tables the onselectionchange should fire. It seems that the last record selected in a table seems te be "remembered" as the selected record for both table, while the memory of the currect selected record should be there for each table separate. So I consider this as a bug or at last unexpected behaviour.
Correct woud be:
Step 1: Table A, record one
Step 2: Table B, record two
Step 3: Table A, record two (fire onchange)
Step 4: Table B, record two (no fire of onchange)
Step 5: Table A, record two (no fire of onchange)
1) Does somebody see a work around for above problem? I already put then in differents forms, did not make a difference.
2) Can I get this on the bug list?