sap.ui.table.Table: Threshold ineffective on initial load

OpenUI5 version: 1.60.16 (possibly any other) Browser: Chrome 76.0.3809.100 (Windows 10 x64 10.0.18362) Any other tested browsers: Also fails in Edge and Internet Explorer 11 Minimal example: https://output.jsbin.com/manuqavuvu/1 (Disable CORS!)

Steps to reproduce the problem:

1. Use sap.ui.table

   • threshold = 500
   • visibleRowCountMode = Auto

2. Query a larger OData v2 data source

What is the expected result?

The table immediatly fetches data for the first 500 rows. Thus, enabling smooth scrolling through a large portion of these entries without further interruption as described in the API documentation for the threshold property.

What happens instead?

The table fetches additional data way to early, in some cases right after the first or second scrolling. During the fetch, the table’s local busy indicator is displayed, preventing all user interaction. This becomes really annoying if the query actually takes time and blocks the user from scrolling through the remaining 80% of the already loaded data.

Network trace of the minimal example immediately after displaying the table:

1. GET Orders?$skip=0&$top=505 (Correct)
2. GET Orders?$skip=200&$top=500 (What now?)
3. GET Orders?$skip=400&$top=430 (No idea)

This might or might not be related to the OData test service. Yet, the symptoms are identical using on-premise SAP Gateway services.

[Shtilianova]

Hello @janmattfeld , I’ve created an internal incident 2080375757. The status of the issue will be updated here in GitHub. Regards, Diana

[Jordan-Ryan]

Hi,

I am running on version: 1.60.24

I have a very similiar issue, on inital load it calls the service for 113 records (13 visible and 100 threshold) but when I scroll down (past the 13 records) it starts to call the service again, meaning the busy indicator comes and the table is not usable.

Would this be the same issue as mentioned here or would this be slightly different?