Answers

• kthorngren Posts: 21,341Questions: 26Answers: 4,954

  March 2022

  Sounds like you are using draw() or ajax.reload() in an event that occurs after the Editor update response. Using one of these APIs will cause the additional GET request from Datatables. As an example look at lines 94-112 of this example. It has events using ajax.reload(). Look for something like this in your code.

  If you still need help please post your relevant Editor and Datatables code. Better would be a link to your page or running test case showing the issue so we can help debug.
  https://datatables.net/manual/tech-notes/10#How-to-provide-a-test-case

  Kevin
• jorgelaranjo Posts: 5Questions: 2Answers: 0

  March 2022

  I don't have those API as far as I can tell.

  <script>
      var editor; 
  
      $(document).ready(function () {
      editor = new $.fn.dataTable.Editor( {
  (...)
  
      $('#table').DataTable({
              "processing": true,
              "serverSide": true,
              "ajax": "/ajax/endpoint",
  (...)
  </script>
  
  

  I believe the cause is the serverSide setting?
• kthorngren Posts: 21,341Questions: 26Answers: 4,954

  March 2022 Answer ✓

  Yes, I believe you are correct. After the Editor updates the table Datatables wants to refresh the table to update sorting, searching, etc. This causes Datatables to fetch the page data from the server.

  Kevin