Would it be possible to code some sort of hack/fix to produce Popup_key LOV functionality into the built-in tabular form functions. I understand the issue with requiring items to hold both display and return values, but perhaps there is an Ajax solution with a hidden field.
With your apex lib framework the Apex ‘built in’ tabular form function is now capable of producing production quality solutions. The lack of a workable Popup_key LOV solution is the last nut to crack.
There is loads of stuff on the forum:
http://forums.oracle.com/forums/thread.jspa?messageID=1303454�
http://forums.oracle.com/forums/thread.jspa?messageID=1105447􍸧
http://forums.oracle.com/forums/thread.jspa?messageID=1492810�
http://forums.oracle.com/forums/thread.jspa?messageID=1383037�
http://forums.oracle.com/forums/thread.jspa?threadID=457846
Cheers
Simon
Logged In: YES
user_id=1679112
Originator: YES
If this is not possible, a work around could be:
Instead of a POPUPKEY_LOV use a POPUP_LOV with a query that uses the LOV value as both the display and return values. This value can then be used as the foreign key to the LOV table and indexed accordingly. The problem is when the value in the LOV changes, which could be solved with a before update trigger that updates the values in the table.
To support this, it would be good if there was a mechanism to set the POPUP_LOV to readonly. That could probably be incorporated into the Apex lib framework.