OpenEdge Development: Mobile Applications - Product ...

Chapter 4: Creating Mobile Apps using JSDOs
When the operation is complete, any working record for an associated temp-table and
for any child temp-tables is not set.
When you call saveChanges( ) to synchronize changes made by this method with the
database, the AppServer executes the ABL routine that is associated in the JSDO
catalog with the delete operation.
Note: If an error occurs on the server, the record is automatically restored in the
JSDO’s local storage.
Associated ABL routine: Delete
The signature of the ABL routine associated with a delete operation must have a
DATASET or TEMP-TABLE INPUT-OUTPUT parameter.
The following example shows a DeleteOrderEntry( ) method that might be
associated with Mobile delete operations:
METHOD PUBLIC VOID DeleteOrderEntry(INPUT-OUTPUT DATASET dsOrderEntry):
END METHOD.
Client JavaScript code: Delete
The following example illustrates calling remove( ) on a JSRecord object:
/* subscribe to event */
dsOrderEntry.subscribe('afterDelete', onAfterDelete);
var jsrecord = dsOrderEntry.ttCustomer.findById(myid);
jsrecord.remove();
dsOrderEntry.saveChanges();
function onAfterDelete (jsdo , record , success , request ) {
if (success) {
/* for example, get the values from the record that was
deleted to display a confirmation message */
var myKeyField = record.data.myKeyField;
}
else {
if (request.response && request.response._errors &&
request.response._errors.length > 0){
var lenErrors = request.response._errors.length;
for (var idxError=0; idxError < lenErrors; idxError++) {
var errorEntry = request.response._errors[idxError];
var errorMsg = errorEntry._errorMsg;
var errorNum = errorEntry._errorNum;
/* handle error */
}
}
}
};
112 OpenEdge ® Development: Mobile Applications