How to prevent Master navigation when detail has outstanding changes? Currently we check on the |
OK, so I might have a solution :) I can't think of anyway other way, which is why I'm asking here in the hope someone out there has more elegant solution. When the user clicks on a new record in the master grid I check to see if my detail grid has outstanding changes, if it does I raise an exception and store the preivious rowid (ie the row with the outstanding changes associated) in a package variable. I then display an alert and then navigate back to the previous row. I figured this would work but obviously the whole process kicks off again when I set the row back to the previous one... hence the package variable. I use this to check to see if the rowid is the same as the package vaiable rowid, if they match ie we are navigating back to the row that caused the initial error we just don't do anything. It seems to work, but I'm not sure... what do you all think????
Hi Simon, This looks like the right way to me. Kind Regards,
(12 Feb '16, 03:15)
Yalim ♦♦
|