Answers

• allan Posts: 61,716Questions: 1Answers: 10,108 Site admin

  October 2022 Answer ✓

  Thanks for flagging this up. It looks like SearchPanes is resetting the paging on its own initialisation. I don't have an immediate fix for this I'm afraid, but I have logged it so I can look into it. Hopefully for the next SearchPanes release, but I can't guarantee that.

  Allan
• cass Posts: 7Questions: 3Answers: 0

  November 2022

  I've worked around this issue by saving the current page in sessionStorage when the user leaves the screen.

  I then placed this code after the table definition:

  table.on("init.dt", function (e: any) {
      if (sessionStorage.DTCurrentPage !== undefined) {
          let pageNum: number = parseInt(
              sessionStorage.DTCurrentPage
          );
          if (!isNaN(pageNum)) {
              table.page(pageNum).draw(false);
          }
  
          // Remove saved data from sessionStorage
          sessionStorage.removeItem("DTCurrentPage");
      }
  });
  

  Seems to be working well so far. Also, it has the benefit of returning to the selected page even when a filter has been applied, which does not normally happen with SearchPanes even when cascadePanes is set to false.