Response to iXML 1.0 requests

When an iXML 1.0 document is received, the e-Commerce Extension for MEC also ensures that the response document is transformed into a standard iXML 1.0 response document before returning it. For insert, commit and update requests, the responses are identical to those given by versions of Infor e-Commerce that use iXML 1.0. However, the delete response is slightly different.

After a successful delete request, the response document will now include a list of records actually deleted. These are listed in a set of business-object elements, each of which is named after a business object and includes an attribute with the key-field value of the record deleted. Below is an example of a response given after a successful delete operation by the "Product" business object.

<?xml version="1.0" encoding="UTF-8"?> 
<IdealXML version="1.0" xmlns="Response" requestid="UniqueID"> 
	<Response> 
		<Status> 
			<Message code="401"/> 
		</Status> 
		<Product ProductID="2PAR" xmlns="Product"/> 
		</Response> 
</IdealXML>

After a failed delete request, the response document will contain an error code under the <Status> element and no business-object elements, as in the following example:

<?xml version="1.0" encoding="UTF-8"?> 
<IdealXML version="1.0" xmlns="Response" requestid="UniqueID"> 
	<Response> 
		<Status> 
			<Message code="204">The gateway has no response data<</Message> 
		</Status> 
	</Response> 
</IdealXML>

If multiple deletes were requested but only some were successful (for example, because one or more IDs did not exist), then the response document will list the successfully deleted records, but will not mention the failed records. To detect the failed requests, the request document must be compared to the response document.

For search requests, the gateway returns all attributes defined as output in the business object method that is called.