I am facing a problem in record insertion on many blocks. Let suppose there are three blocks A,B and C user is inserting record in block A in the meanwhile user jumps to block B and starting record insertion here and then commit changes. Record insertion on block B is failed because of validation on block A, where user left in between and jumped to block B and form is asking for incomplete entries. However on block B all items are validated but still asking to enter data in block A.
Is it possible that if user enter record in current block and forms insert record in that block and do not validate changes on other blocks. I tried insert_record; built-in in on insert record but not worked. Any idea to get out of this situation i would appreciate.
Your requirement is not clear. Can you explain me few things?
How about asking user if he wants to finish the row, or he wants to clear it? You can ask that on leaving the unfinished row, or in code that checks the state of the row and gives that warning you mention. I don't think that one form is intented to work with partial commit. If data is independent of each other and can be commited separately, maybe you should have several forms insted of just one.
The situation is like user may leave a row uncompleted and jump into another block for record insertion there on that block. It is like i have three fields having attached LOVs normally user will be picking data from LOV but if information not found in LOV then user would have to insert that information too so this block B is placed on another canvas and and another window, user open-up that window(Block) and entering all information and attempting to save this data because until this new record is not saved in database, newly added record would not come in LOV. And commit is invoking validation on first block and this second block too.
Anyone could suggest any better solution.
A form-module is treated as one unit of work or one transaction. Either you save all data in it or nothing. If you have logic which should be saved separately from each other, then you should design your modules accordingly, in your case, create different form-moduls for the different blocks. Everything else will only cause problems and is not the way forms works.
Nachricht geändert durch AndreasWeiden
The right way to do it is to make another form with that other block, for insertion of data that will appear in a LOV. Call it using separate session, and commit it there. For the user there'll be little change, since you'll open another window anyway. There is no reason to, even if it is possible, force solution using just one form.