CRUD Delete

ZingGrid has default behavior for delete actions. There are expected inputs and outputs for a delete action. You can, of course, extend or override this default behavior.

CRUD Defaults

The default send and return values for CRUD actions are:

Override Defaults

If you need to override any default delete actions, you can use deleteOptions to adjust all actions against the initial and subsequent fetches from the grid. You can read more about available deleteOptions values here.

Here is a list of available deleteOptions:

{
  // to change the read method of the action to POST
  "method": "POST",
  // takes a JSON packet to be sent to the server in place of the action
  // in this case user_id is always one.
  "body": {user_id:1},
  "requestType": "application/json",
  "exclude": "",
  "headers": {"Authorization": "Basic super-secrete-key"},
  "mode": "no-cors",
  "responseType": "",
  "src": "",
  "queryString": ""
}

The body value can be a static JSON:

<!-- basic delete option with static body -->
<zg-param name="deleteOptions" value='{"body": {"user_id":1}}'></zg-param>

The body value can also be a function which returns an object, like so:

<!-- basic delete option with function reference for body -->
<zg-param name="deleteOptions" value='{"body": "_fncStringReference"}'></zg-param>

// function returns an object
function _fncStringReference(record) {
  return {
    // to change the read method of the action to POST
    method: 'POST',
    // takes a JSON packet to be sent to the server in place of the action
    // in this case user_id is always one.
    body: {user_id:1},
    requestType: 'application/json',
    exclude: '',
    headers: {"Authorization": "Basic super-secrete-key"},
    mode: 'no-cors',
    responseType: '',
    src: '',
    queryString: ''
  }
}