cancel
Showing results for 
Search instead for 
Did you mean: 

Performance problems while using ScrollContainer

Former Member
0 Kudos

Hi,all

I'm using a ScrollContainer UI element in order to display a table with all of its rows at once in a scrolling mode.The table is large(800 rows) and it leads to performance problems.

How can I improve a performance in this case?

Regards,

Michael

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

That's the disadvantage of using a scroll container around a table that shows all rows instead of using the default paginators. In NW 7.1, the table will have its own scrollbar and only the visible rows are sent to the browser.

Armin

Answers (1)

Answers (1)

former_member197348
Active Contributor
0 Kudos

Hi Michael,

If you load and show 800 records in one call, it will definitely takes more time. As a workaround try like this: In initial call just show the table with 10 or 15 rows. Put a ToolBar button in the table toolbar .You can create an action to open and close the scroll container and bind this to ToolBar button.

regards,

Siva