|
Re: WHEN-VALIDATE-ITEM for a non-navigable item [message #657777 is a reply to message #657776] |
Tue, 22 November 2016 07:49 |
cookiemonster
Messages: 13960 Registered: September 2008 Location: Rainy Manchester
|
Senior Member |
|
|
yes.
WVI firing is based on the items item_is_valid property. Before a row can be saved to the DB all items in the block need to have that property be true. It gets to be true by passing any validation attached to it - mainly WVI, but also certain properties - format mask, required.
Normally forms fires the WVI as soon as you navigate out of a field, or when you press save. First doesn't apply in this case, but the second does.
|
|
|
Re: WHEN-VALIDATE-ITEM for a non-navigable item [message #657778 is a reply to message #657777] |
Tue, 22 November 2016 07:51 |
cookiemonster
Messages: 13960 Registered: September 2008 Location: Rainy Manchester
|
Senior Member |
|
|
All that said, if the field isn't visible then presumably it's getting its value based on what happens to another field(s) in which case it may be simply to just do the necessary validation on those.
It's hard to say without knowing how the field gets populated and what validation needs doing.
|
|
|
|
|
|
|
|
Re: WHEN-VALIDATE-ITEM for a non-navigable item [message #657787 is a reply to message #657782] |
Tue, 22 November 2016 14:42 |
|
Littlefoot
Messages: 21823 Registered: June 2005 Location: Croatia, Europe
|
Senior Member Account Moderator |
|
|
adfnewbie
(I am not sure how this happens.)
If you wonder how to find that out, set a breakpoint into one of PL/SQL program units (if nothing else, create a WHEN-NEW-FORM-INSTANCE trigger, put NULL; in it and set a breakpoint to that statement by right-clicking the left PL/SQL window margin). Then run the form in debug mode and follow its execution, step by step.
|
|
|