By default Editor will use the tr element's id attribute to identify the row to the server (more specifically this will typically contain the database's primary key to uniquely identity the row). While this default method can be very useful, particularly if you use the DT_RowId JSON option to set the id, you may wish to read the row's id from the JSON data source, rather than the DOM. This is easily done using the srcId option.
The example below, with srcId is set to id is suitable for cases where the data source objects look like: { "id": 2, "browser": "Chome", ...}. Like other data source options the srcId option can be given in dotted object notation to read nested objects.
| Browser | Rendering engine | Platform(s) | Engine version | CSS grade |
|---|---|---|---|---|
| Browser | Rendering engine | Platform(s) | Engine version | CSS grade |
The Javascript below is what is used on this page for the example shown.
The HTML shown below shows the TABLE that is used in this example.
The code below is that HTML that is used to drive the server-side section of this exampe.
The HTML shown below includes the Javascript and CSS files that are required for the Editor operation on this page. You can use this as a template for your own pages, but if you move the files you might need to update the paths.
Editor submits and retrieves information by Ajax requests. The two blocks below show the data that Editor submits and receives, to and from the server. This is updated live as you interact with Editor so you can see what is submitted.
The following shows the data that has been submitted to the server when a request is made to add, edit or delete data from the table.
// No data yet submitted
The following shows the data that has been returned by the server in response to the data submitted on the left and is then acted upon.
// No data yet received
DataTables can request information to display from the server when the page first loads. The block below shows the response from the server.