PeopleSoft Timing Out and Logging Out Because of a Huge Number of Rows in Level 2 Grid

I have a component (Territory Management) in PeopleSoft. Now there is one territory in which there are around 13000 rows (Sales Users) in Level 2 grid (Record: RSF_TR_TEAM).

While we give the search key values (Tree Name and Territory ID), the page times out and it logs out of PeopleSoft due to the huge data. It is working fine when the number of rows in Level 2 grid are less (checked for less than 1000).

I need to handle this some way, so that rows can be inserted and deleted from the grid, without any issue.

Popular White Paper On This Topic

Try checking the No Auto Select check box on the grid properties and then fill the grid manually based on key information needed to fill the grid. You may also, in addition to , instead of first suggestion, look at where the table is getting its data and see if any indexes can help. Many times it is not the rowset amount (although 13,000 is a large number), but the drag on getting the data from the system. I know we have a few grids here that fill up with about thousands of rows with no issues.

I tried the first solution, and I was able to show the page with all 13000 rows in the grid. (Rejected rows in RowSelect event and then used RowSet.Select() method to populate the level 2 grid). I cannot filter the number of rows, as the requirement is to show all the 13000 rows to the user.

But, the problem comes when we delete (Click on -) on insert (Click on +) a row. At that time, it again times out.

Regarding indexing some additional columns (if I correctly got your point), there are only 4 columns, of which one is already indexed properly.

I have an issue with a functional design that presents such a vast amount of data to the user in a grid. I mean really, are they actually going to visually ( and hence mentally) absorb that many rows of data?

Is there not a better method to fill the grid based on additional criteria?

Thanks for the reply. The page design is absolutely fine, and it is a delivered one. However, over a period of time, a large number of sales users have been added to this territory, resulting in a huge number of rows.

The only job of the user//admin would be either
(1) to find a sales user using the "Find" feature of the grid, and delete that row,
(2) to add a new sales user to that group.

<rant>Obviously the page design is not "absolutely fine." It's timing out the server and killing the user session. One user is tying up an app server process for whatever time it takes to time out. And the user is sitting there doing nothing while that is happening.</rant>

I would:
Run traces to be sure I know where the bottleneck is.
Try to sell the business on adding a new filter to limit the rows. Maybe pre-query to count the rows before filling the grid and warn to add additional filters if the count is too high.
New page for adding sales users that doesn't have to fill a grid first.

Or archiving the "old" data off to a secondary table, splitting the sales region into a smaller region so that not all 13000 get loaded at once.

I remember when one client sued PeopleSoft over the apparent "failure" of the product, PS had a stock standard response along the lines of "PeopleSoft has been optimised for a generic business situation. This means that under certain circumstances, it is highly appropriate for the client to alter modify the process using PeopleTools to better suit their needs"

Anybody who says they need to see all 13,000 sales people on this screen, should be asked to name the first 800 people. Most likely they want all 13,000 in the grid because they want an Excel export and can't be bothered to run a report.

Copyright 1998-2015 Ziff Davis, LLC (Toolbox.com). All rights reserved. All product names are trademarks of their respective companies. Toolbox.com is not
affiliated with or endorsed by any company listed at this site.