I have a Form where i have a grid having 5-6 columns and the array used to popul

ambrishs over 11 years ago

I have a Form where i have a grid having 5-6 columns and the array used to populate this grid may have large number of records around 600-1000. The issue is page loads very-very slow and becomes un responsive for 2-3 minutes. I know we have option to use paging grid, but the array i am getting is coming as output of an stored proc. so I can not use Datastore here to pull arrays. Any suggestions to improve the performance. Thanks....

Discussion posts and replies are publicly visible

0 akhilan over 11 years ago

You could still use Paging Grid by using todatasubset(). This allows you to display data on Paging Grid using the data from multi value PVs. Here is a link to it forum.appian.com/.../Appian_Scripting_Functions
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 ambrishs over 11 years ago

Thanks Akhilan. Is this function available for 6.6 version. I do not see it in Appian Scripting Functions list.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 akhilan over 11 years ago

It is available 6.6.1 onwards.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 ambrishs over 11 years ago

Any other suggestions, for this since i am using 6.6.0 and i do not see this function.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Myles Weber
Appian Employee
over 11 years ago

6.6.1 is a required update to 6.6.0. I recommend applying.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Mike Cichy
Appian Employee
over 11 years ago

You could rectify your stored procedure to accept additional filtering parameters. If the result is in hundreds of rows, what is the end user going to do with them?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Sathya Srinivasan
Appian Employee
over 11 years ago

I second Mike's suggestion. Showing 600 records in a form is not a really useful user experience. Statistically, information above 20 records becomes useless for the viewers. I suggest you modify the SP to accept a paging parameter and return the defined data set to maximise UX.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 ambrishs over 11 years ago

Thats understandable. but in our situation user is trying to look for users(may be upto 600-1000) under a Firm, and then select a few of them to take action. We wanted to give them option to select users by seeing them, instead of entering user names, where there is possibility of making type etc.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Medhat Galal
Appian Employee
over 11 years ago

How are they trying to look for a user or users in 600-1000 users? Should they search? Or at least return users alphabetically? Users A-C, D-F, etc

Also, I will repeat what was said before, at least upgrade to 6.6.1 or later as soon as possible.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 ambrishs over 11 years ago

It's sorted alphabetically. But page scroll is very-2 slow with 600 or so records.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel