Editor: on Delete, can I control what fields are send with the Ajax JSON object to the server?

Editor: on Delete, can I control what fields are send with the Ajax JSON object to the server?

atcclearsatcclears Posts: 24Questions: 7Answers: 0

I'm including several hidden fields in the table. One is a session ID and another is a last-updated timestamp. The latter is used for concurrency control.

On Edit, both hidden fields are included in the JSON object going to the server. Great!...

...but on Delete, only the session ID field is being send over.

Is there a way to tell Editor what fields should be included in the JSON object?

I am already using the preSubmit function to include some other fields that are common across all records in the table. The last-updated timestamp would be unique to each record in the table.

This question has an accepted answers - jump to answer

Answers

  • allanallan Posts: 61,777Questions: 1Answers: 10,112 Site admin
    Answer ✓

    Currently only the row id's to be deleted are automatically sent by Editor when deleting data, since that is all the Editor libraries need to delete the rows on the server. However, I realise this isn't always enough and 1.5 will add the data for the rows being deleted.

    Until then preSubmit is how you would add additional data.

    Regards,
    Allan

  • atcclearsatcclears Posts: 24Questions: 7Answers: 0

    Allan, thx.

This discussion has been closed.