BUTTON CLICK ON SEARCH ITEM CAUSES OTHER REGIONS (FORM) IN TABLE TO ERRORS

Question

Hello,
I dont know if I have come to a limitation or flaw of the XE or is it me who does not know how to. (probably me)
The thing is that I have in one page, one standard form for entering data and one report output table to show them. This output table has incorporated that built-in feature of Search
Now, what happens, if I click on the search button to locate a record in the Report table, as the full page reloads, then the Form region also loads but as it has no data, in the effect of being reloaded activates its button of submit, bringing my report table to all errors as it is getting null values which are not allowed. I really need the search feature because otherwise users can have the more and more unconfortable time to locate things as the table grows to thousands of rows.
any help would be greatly appreciated
kindest regards
Alvaro

Answer 1

Hi,
My first option probably do not even work. I did mean put expression "GO" as I understand go button submit request GO.
And now when I think it is validations that gives those errors. Right ?
So you need set that condition "PL/SQL function body returning a Boolean" to after submit validations
RETURN :REQUEST IN('SAVE','CREATE');Sorry, about confusion
Automatic Row Processing (DML) process that actually insert/update/delete is anyway run only when certain submit requests
>
Valid Update Request Values: SAVE, APPLY CHANGES, UPDATE, UPDATE ROW, CHANGE, APPLY, APPLY%CHANGES%, GET_NEXT%, GET_PREV%
Valid Insert Request Values:      INSERT, CREATE, CREATE_AGAIN, CREATEAGAIN
Valid Delete Request Values: DELETE, REMOVE, DELETE ROW, DROP
>
Br, Jari