Objects Exposed

The Amazon Connector outputs the following objects which can be consumed by other tools:

• InputData — The InputData node is only available when another task step provides the consumed Data Source (see About the General Tab). When consuming a recordset, this node lists the recordset columns; for XML, it contains the XML document received by the Amazon Connector.
• OutputData — The OutputData object contains two sub-objects:

• XmlString — This is the XML document produced by the tool, containing data returned from Amazon. Also included are the key fields for the mapped elements affected by the used operation and a SupplementaryReference field for task auditing purposes.
• XmlSchema — This contains the output schema in XSD format.

• ErrorData — The ErrorData object also contains two sub-objects:
  • XmlString — This contains any error data reported by Amazon

    <Error> — The ErrorData object also contains two sub-objects:
    Error — All errors are created as an node, with the following sub-nodes:
    <Object /> — The name of the requested object
    <CODE /> — The error code returned by Amazon Connector
    <MESSAGE /> — The corresponding error message
    <EXTENDEDINFO /> — A string containing additional information about the error
    <INPUTDATA /> — The header input data (excluding child nodes) mapped for the object, plus all data contained in SupplementaryReference
<Error>
    For more information about the errors received, see Error Handling.

  • XmlSchema — This contains the output schema in XSD format.
• Step Properties — Standard step properties are also available allowing you to use statistical data of the Amazon Connector step.

Where can the XML Output be Used? #

The incoming XML is translated into the XML format for the object and operation selected in the configuration. The data for the linked fields is brought across into the output XML — only those fields that are linked are brought across. The XML is passed to the Connector, which then:

• Processes the data
• Performs the operation requested
• Receives an XML document containing the response

Both the OutputData and ErrorData documents can be directly used by succeeding task steps that can consume XML data, as part of an application integration or synchronisation process. To use the documents in a non-XML consuming tool, use a Convert XML to Recordset step first to create a recordset copy of the XML data.

The XML documents are also available as consumable objects from the Task Browser (XmlString). When used in a task step, such as Format as Text or Save File, this exposes the actual XML string.

Error Handling #

Errors are written to the BPA Platform Event Log (Tasks toolbar > Event Log ). You define how errors are handled in the Options tab of the tool (see Options Tab).

Reasons for the errors could include:

• Web service connection errors
• User privilege errors
• Errors, messages, and warnings from Amazon Selling Partner API
• Any reported task runtime errors, such as, loss of connection