Cascading LOV performance
695278Jun 2 2010 — edited Jun 4 2010I am struggling with a cascading LOV. Say I have items :PX_SYSTEM_ID and :PX_OBJECT_ID. When I change the first the LOV for the second should be changed. To do so I am using the example with ajax and an application process of which there are lots of examples on the internet.
However: On :PX-OBJECT_ID an LOV is defined containing a large list of objects. The AJAX script also creates an LOV with a large number of objects. Separately both queries work fast (within 2 seconds which is fine). However Apex checks the values returned by the AJAX script with the values in the LOV on the item. This is killing for the performance (in Internet Explorer). (Takes over 35 seconds) In Firefox and Chrome it performs OK.
There is another issue: When the values in the LOV on :PX_OBJECT_ID are eg 1,2,3 and the values returned by the AJAX script are 4,5,6 the LOV on :PX_OBJECT will be empty after the AJAX script has run.
Any clues?
Kind Regards,
Maurice Niezen