skip to main content
OpenEdge Mobile 11.5.1 Updates : Behavior changes in the OpenEdge JSDO
 

Behavior changes in the OpenEdge JSDO

Since OpenEdge 11.5 was released, a feature of the OpenEdge JSDO has changed its behavior from what is documented in the OpenEdge Release 11.5 documentation. As currently documented, when a JSDO object is created for a ProDataSet resource that supports before-imaging, any Mobile create, update, delete, or submit operation can have a successful result with errors returned in the changed records. That is, it is documented that after invoking the JSDO saveChanges( ) method, the success property of the request object returned from the server for each Mobile operation on before-image data can be true and the associated change record can also contain an error string. You can then return this error string using the _errorString property accessed from the data of the change JSRecord object or using the getErrorString( ) method invoked on the change JSRecord object.
The undocumented change in behavior since OpenEdge 11.5 is that this error string can only be found in a change record when the success property returned in the request object is false, like any other error returned from a Mobile operation. With this change, the success property behaves consistently, returning true only when no errors are returned for the Mobile operation, and returning false when any errors, from any source, are returned for the Mobile operation.