This content has been marked as final. Show 4 replies
Change your display only items to hidden items (not protected). This will allow your page processing to work.
Then create new display only items (do not save state). Then have Super LOV update both the display only and the hidden items.
Hm, didn't think of that, that should work. Thanks!
Dan - That takes care of the page processing but when the page refreshes, the display-only items remain blank because they don't save state. How can we have our cake and eat it too? I guess we can use the Source attribute of the display-only items to fetch the value or something like that but that would mean repeating the LOV query, not ideal for maintenance.
When the LOV pops up, all the extra columns are useful to identify the row you need. In some cases, it helps to show those values on the page to provide some additional context but because of this new SSP lockdown in 4.x, the display-only items can't save state.
Curious, when you designed this "return items into" feature, what use-cases did you have in mind?
If you would like the superlov to perform the value fetching on page load then you could do that:
Is what i usually do. Second parameter is the return item value.
The getValuesByReturn and setValuesByReturn methods can be used to programmatically fetch return values and set the item using the return values. getValuesByReturn will return a JSON object with the results from the fetch. setValuesByReturn goes a step further using the return values to set the display and return values for the item. Example(s):
Now this isn't without some drawback and that would be that the values in the display items will only popup after the page has loaded and the values have been retrieved by the plugin. It will however save you from changing the item source to a sql query. See how it goes.
$('#P1_ITEM_NAME').apex_super_lov('getValuesByReturn', '101'); $('#P1_ITEM_NAME').apex_super_lov('setValuesByReturn', '999');