Data Change Notification Results

Each binding in a data change notification (DCN) request is associated with an ID. The result status of the DCN request is returned in JavaScript Object Notation (JSON) format, and includes a list of IDs followed by a Boolean success field and status message, in case of error.

The processing of the individual messages within a DCN request is done as a single transaction. A failure of one message results in the changes from all preceding messages being rolled back and all following messages are skipped. In response to payload and MBO operation DCNs, Unwired Server sends the requester a JSON string containing details about the success and/or failure of the operations. These examples show the JSON-formatted result for a multi-message DCN request, and has been formatted using newlines, and indentations, which are not present in an actual response.

This is an example of a response message for successful processing of a request containing four individual messages, using id values {1, 2, 3, 4)

[{"recordID":"1","success":true,"statusMessage":""},
{"recordID":"2","success":true,"statusMessage":""},
{"recordID":"3","success":true,"statusMessage":""},
{"recordID":"4","success":true,"statusMessage":""}]

In this example the third message in the request contains an error:

[{"recordID":"1","success":false,"statusMessage":
"Changes rolled back because dcn message with ID 3 in the DCN request failed."},

{"recordID":"2","success":false,"statusMessage":
"Changes rolled back because dcn message with ID 3 in the DCN request failed."},

{"recordID":"3","success":false,"statusMessage":
"VirtualTableName is null. MBO name Departments might be incorrect or with missing 
capitalization in the DCN request"},

{"recordID":"4","success":false,"statusMessage":
"Processing of DCN message skipped because dcn message with ID 3 in the DCN request failed."}]