Large ResultSet in a WD Table

[former_member187167]

Hi,

Are there any best practices to bind a large result set to a web dynpro table?

The problem is that there is no event in the table for reading next page of records.I could not bind the buttons in the footer to some event.

The API we use has methods like <b>getResult(int startingRow, int count)</b>, but I don't know in which moment to call them. There are no events on scrolling between elements.

The only workaround we have found, is to have some calculated field in the context node bound to the table.

And when the method <b>getXX(IWDElement)</b> is called, we know we have to make another get() to back-end to obtain another chunk of records.

The other possibility might be to use external buttons for paging, not the default ones in the table footer.

But all these are workarounds, I think there should be some common solution.

Thanks in advance and regards

Konstantin

[former_member182372 · Accepted solution]

Hi Konstantin,

There is a property in Table UI element called firstVisibleRow. So, bind it to calculated attribute and in setter method do your swapping logic.

Best regards, Maksim Rashchynski.

[former_member187167 · Accepted solution]

Thanks Maksim,

That sounds great!

Just one question - when will this setter be invoked? Is this done automatically, on each and every scroll?

Regards, Konstantin

[former_member182372 · Accepted solution]

Hi Konstantin,

Yes, exactly. When first visible row in a table is changed (by pagination) this setter is invoked.

Best regards, Maksim Rashchynski.

[BeGanz]

Hallo Konstantin,

look at this: [Web Dynpro Java Table Paging Unleashed: Optimizing Heavy Table Performance|https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/12130] [original link is broken] [original link is broken] [original link is broken];. This also applies to NetWeaver 04 and 7.0.

Regards, Bertram