• Type: Sub Task Sub Task
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.3
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-10086Continue Server Side Paging Work - Stacked Collection
      KULRICE-10112docs and smoke test for server paging of collection results
      KULRICE-11935Library Collections Lookup sample (server side paging) has no rows returned
      KULRICE-11071KRAD Demo Library Collection Features Server Paging Stacked Collection with server-side paging and Table Collection with server-side Paging not paging
      KULRICE-13083Implement a way to set up server side custom sorts for server side paging collections
      KULRICE-10977Multi Value Lookup : Implement server side paging for both rich and non rich tables when data selected is not on current page
      KULRICE-5599Multi-Value Lookups: Implement Select/Deselect All Pages
      KULRICE-9786Force server errors for fields to show on page change
      KULRICE-11936Library - Collections - server side Paging (rich table only) - records displayed, then disappear
      KULRICE-13886Fill AFT Gap: Server Paging - Stacked Collection with NextPager
    • Rice Module:
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required


      Currently the paging for large collections is done all client side, so all the data is sent and rendered initially. Performance could be improved by fetching and render each page as requested. This will involve hooking into the paging functionality of DataTables.

        Issue Links



            • Assignee:
              Peter Giles (Inactive)
              Jerry Neal (Inactive)
            • Votes:
              0 Vote for this issue
              1 Start watching this issue


              • Created:

                Structure Helper Panel