We're using XML tables to populated chaing list boxes. In one case I've a set of 6 boxes that are chained with upwards of 17000 rows of data built to populate the dropdown. Periodically the functionality of the drop downs stops working and another window pops up and display the XML code behind the boxes.

Does anyone know if there is a hard limit on the number of rows and/or columns that can be used in an xml table to populat chained controls?

I've included a sample of the code we've written to generate the xml table. Then the code procedured is called from the control on the HTML page to dynamically populate each chained control.



TABLE FILE V_CUSTTRND
SUM
SLS_FYPER_DT
PRODGRP_NM
PRODLINE_NM
GEOG_NM
AREA_NM
CUST_NM
BY HIGHEST SLS_FYPER_DT
BY PRODGRP_NM
BY PRODLINE_NM
BY GEOG_NM
BY AREA_NM
BY CUST_NM
ON TABLE PCHOLD FORMAT XML
END

Laure,

I had two cases opened for 761 that were related to ibirls2 and html pages. Both were fixed in 762, Hot Fix 3, which we went production with. Both cases had to do with the number of entries being loaded into a dropdown box.

If you need the case numbers, let me know.

Ginny,
Can you provide the case number so I can research this farther. We're in the process of upgrading to 7.6.4 and are experiencing the issue there too. If you hot fix was in 762 I would expect it to be part of 764 also.

Thanks,
Laure

Laure,

There were two cases, each with a little twist: 32042546 (After conversion, htm page gets script timeout message) and 32042527 (Procedure-driven dropdown box not being populated).

The first one was related to size of answer set. The second was related to new pages created in 762. Both were fixed in 762 Hot Fix 3.