963510 wrote:If I understand your scenario correctly, you are having a on-submit pl/sql process to take care of the database insert/update/delete. The process is being triggered from a button, lets say "Submit". The "Submit" button is displayed only if the value of page item P24 is not null. All good till here.
I am trying to mimic the Multi Row Update process to a tabular form while adding a slight twist. Lack in understanding is killing me. There are a couple parts involved.
I have a tabular form. Besides the Add and Delete buttons to the tabular form, I have added a button that is only displayed if a page item (P24) is Null. This button is supposed to insert data into the tabular form/database table, however, on a condition.
There is another page item (P1) that determines if the data can be inserted into this table. If P1 is also Null then a dialog box is displayed (warning message) and doesn't allow the insertion of data to continue. It just stops you and keeps you on the current page.Why can't you write a simple validation on the page item P1 that displays an error message the time the user hits the "Submit" button and the value of the page item is null?
Is this accomplished with a PL/SQL procedute?Yes, as explained above.
Does the actual conditional of the insertion of data get stored in the PL/SQL?You can always put a condition on your pl/sql process such that it executes only when the value of page item P1 is not null.
963510 wrote:The validation would be useful if you wish to throw an error message to the users. Otherwise, you can just condition your pl/sql process (that updates the database) to execute only when the value of the page item P1 is not null.
My only concern/issues is how would the validation be used. P1 is an item derived from a query on a table, and this value can be NULL.
So would using a validation still be useful here?