Row Selector Checkbox in Report throws "wwv_flow.accept" Error when checked

Question

Hello all,
I ran into some time consuming trouble on
a page of an assistant flow contains a report regions. Users shall select one or many rows from the report.
The checkbox was added as a linked column and formatted as "Simple Checkbox".
After submitting to the "NEXT" page an item :Px_MYEVENTS shall collect the ID column value of all selected rows.
The page process "After Submit" shows:
+:P2_Myevents := apex_util.table_to_string(apex_application.g_f01,';');+
It is expected that only selected rows appear on the item, because we need this for further activities.
On testing strange things happens:
If no selection is done, the target page appears, the item :Px_Myevents contains the values of all rows
When a selection is done, the branch error "wwv_flow.accept" appears, :Px_Myevents doesn't contain a value.
This throws even when the code is used as a DA of type PLSQL - statement or function
How do I get the expecte behaviour?
Edited by: F Lan on 27.09.2012 13:18
Apex Version is 4.1.1 on Oracle 11GR2 XE
Remember the milk ;-)
Regards

Answer 1

Hi,
Always state
<ul>
<li>Apex Version</li>
<li>DB Version and edition</li>
<li>Web server used.I.e. EPG, OHS, ApexListner Standalone or with J2EE container</li>
<li>When asking about forms always state tabular form if it is a tabular form</li>
<li>When asking about reports always state Classic / IR</li>
<li><b>Always post code snippets enclosed in a pair of &#123;code&#125; tags as explained in FAQ</b></li>
</ul>
The following line ought to work they way you want it to , I have used this construct without issues
:P2_Myevents := apex_util.table_to_string(apex_application.g_f01,';');
If no selection is done, the target page appears, the item :Px_Myevents contains the <b>values of all rows</b>This suggests that all checkboxes are being treated as checked.
You need to check why they are being treated as checked. Depends how they are rendered and if they are being manipulated in some way.
The other point to consider is the Processing Point. The above process must run before ApplyMRU/ApplyMRD.
You could try running the form in debug mode to see if it revealing anything in the Debug Report.
The other way is to put it up on apex.oracle.com for someone to take a closer look at it.
Cheers,