Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

"Index out of bound" List View with Pagination - HTTP headers

SA-1805

Summary



Paginating over a list view with a big number of parameters it's failing fails after page 4. The report is failing when the String parameter is too big. The same report was working fine on PRPC 5.2.

Error Messages



Index out of bound exception.

 

Steps to Reproduce

Create a listview with a string parameter.

 

The parameter is of the type "value1","value2","value3",...,"valueN".

 

Set a big number of values in the parameter (50 or 100).

 

Set pagination in the report and a page size of 250.

 

Generate data for the report to be able to present more than 4 pages.

Run the report.

Root Cause



The root cause of this problem is software use/operation error. TheGET request sent to the server gets truncated because it is too big, causing the error.
The customer has custom code which is fetching duplicate usernames and passing that list to one of criteria of the list view (Note:-Around it is fetching 400 users) so that STRURL length exceeding the limit.

Resolution



This issue is resolved through the following local change: 
Customer 
has removed duplicate usernames, now length of STRURL has been decreased and they are not getting “Array index Out of bound Exception”.
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us