The pagination wouldn't available when iTotalRecords != iTotalDisplayRecords

The pagination wouldn't available when iTotalRecords != iTotalDisplayRecords

tfcheungtfcheung Posts: 2Questions: 1Answers: 0

In my case:
It used DB to count all data and set the number to iTotalRecords.
We designed to get the number of records based on start and length from DB, and used OFFSET and FETCH NEXT for it.
Then assigned the number of records into iTotalDisplayRecords.
And then the table will not allow me to select the pages. It only displays one page.

But when I set iTotalRecords and iTotalDisplayRecords are the same numbers, the pagination will be available

Answers

  • kthorngrenkthorngren Posts: 14,128Questions: 25Answers: 3,331

    The Server side processing docs explain what the parameters should be. Sounds like you are setting the iTotalDisplayRecords to the size of the page being displayed not the total records available.

    Kevin

  • tfcheungtfcheung Posts: 2Questions: 1Answers: 0

    What I gave the number to iTotalDisplayRecords is the number of records after filter.

  • kthorngrenkthorngren Posts: 14,128Questions: 25Answers: 3,331

    Please use the browser's network inspector to collect the JSON response when the paging buttons aren't correct. Paste the response here so we can take a look.

    Kevin

Sign In or Register to comment.