A boolean that when set to true indicates that the Data Object resource operation was successfully executed.

This property is set from the HTTP status code returned from the server. A successful resource operation returns an HTTP status code in the range of 200 - 299, with one exception. An unsuccessful resource operation causes a value outside this range to be returned for the HTTP status code and sets this property to false. In addition, a record-change operation (Create, Update, Delete, or Submit) on before-image data that returns an HTTP status code of 200 OK, and returns a record object with a before-image error message is also unsuccessful, and sets this property to false.

Data type: boolean

Access: Read-only

Applies to: request object

The success property is available only for the following JSDO events or in the request object returned to a jQuery Promise callback:

  • afterCreate
  • afterDelete
  • afterFill
  • afterInvoke
  • afterSaveChanges
  • afterUpdate

In the case of an afterSaveChanges event, the success property is true only if all record-change operations that are invoked by the saveChanges( ) method were successfully executed.

This request object property is also available for any session online and offline events that are fired in response to the associated resource operation when it encounters a change in the online status of the JSDO login session (JSDOSession or Session object). The request object is itself passed as a parameter to any event handler functions that you subscribe or register to JSDO events, any returned jQuery Promises, and to the online and offline events of the session that manages Data Object Services for the JSDO. This object is also returned as the value of any JSDO invocation method that you execute synchronously.

Note: For an OpenEdge resource, when the server routine that implements a resource operation raises an unhandled error, this causes an HTTP status code of 500 and any included error information to be returned from the server. This can occur when either an ABL routine raises an application error or the ABL virtual machine (AVM) raises a system error, and the error is thrown out of the top-level server routine.

See also:

fill( ) method, invocation method, invoke( ) method, saveChanges( ) method